-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
certificate signed by unknown authority bug when self-hosting hugoDocs #4
Comments
Thank you very much for your feedback. I was able to reproduce the errors using all images based upon Alpine and Busybox. I've made some changes and triggered build of version 0.49.1. Could you please verify the new 0.49.1 image(s) fixes your problem so I can move on to images with 0.49.2? I'm happy to see you are making use of the image(s) according to your needs, which is very much in line with my intention. |
yes it works for me. Output:
|
I spent a few days trying to get hugo with extensions to compile and run in alpine linux...but finally gave up (would get periodic segfaults!! but sometimes it ran okay). Your docker builds solve that problem, (I'm guessing that's the reason for the
FROM frolvlad/alpine-glibc:alpine-3.7
?) so thanks, and great work.However, I just came across a bug trying to self-host the hugoDocs website.
To reproduce, clone the hugoDocs site, then do:
(ah, note that I'm exposing 1313 to 1314 externally because I'm running my dev blog on 1313...)
To solve, I copied your alpine ext Dockerfile and then added
With that change, hosting the hugoDocs website works:
I think this will have to be done in the final images in your setup, since the ca-certs might be different in busybox/alpine/ubuntu/etc. So no pull request from me, as it seems like something for you to decide where to put it best.
(I also fiddled with a few other things in the Dockerfile, which is why the source is /home, --user is 1000, etc...but those aren't bugs)
The text was updated successfully, but these errors were encountered: