-
Notifications
You must be signed in to change notification settings - Fork 39
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
Name resolution failure at final restart #58
Comments
This seems to be a DNS issue between the docker containers: the It usually has to do with the /etc/resolv.conf file (on the host, which gets copied into the container). Maybe this thread can help you troubleshoot: https://stackoverflow.com/questions/44761246/temporary-failure-in-name-resolution-errno-3-with-docker Ping is not present in the image, but wget can be used to see if the name can be resolved:
|
Hmm, okay.
But on the host:
But I also noticed the control container is stuck in a restart loop and is failing its script.
|
Possibly also is the solution for #58 ?
That last bit with I don't think that the docker internal DNS issue on Ubuntu 22.04 will be solved by that, but it looks like I have now reproduced the |
Hello,
I just installed LabCA on a fresh Ubuntu 22.04 server.
After installing and finishing the setup on the web, it is stuck at the final restart ("Now we will request a certificate for this website and restart one more time...").
In the boulder-labca-1 container I always get this error spammed:
Name resolution should be working. Is there any special record I could have forgotten? I have a CAA record and an A record.
If you need any more logs I am happy to provide them!
Thanks!
The text was updated successfully, but these errors were encountered: