-
Notifications
You must be signed in to change notification settings - Fork 82
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
Strange problem on Docker container restart #18
Comments
Has anyone seen anything like this? |
@janeczku, are you able to weigh in on this issue? Would you like something more specific to recreate it, like a Dockerfile for or something? |
@janeczku I'm also experiencing this same issues on my production server, any suggestions on how I can fix this? |
@smebberson Can you share your Dockerfile and the content of /etc/resolv.conf both from the host and container? |
1 similar comment
@smebberson Can you share your Dockerfile and the content of /etc/resolv.conf both from the host and container? |
Fixed in 0808cf7 |
I have encountered a strange issue that only occurs on Docker container restart. The following describes the lifecycle of the Docker containers.
docker-compose up -d
.app
container throws an uncaught error and the container quits (programmed to be this way).restart: always
policy for the container, Docker compose brings the container up again.Have you seen/heard/witnessed anything like this before?
Here are the logs for go-dnsmasq the first time around:
Here are the go-dnsmasq logs upon automated restart (note: the first part of the logs are from the first run above but you'll see the line where go-dnsmasq restarts and it all goes bad):
System details below:
Let me now if there is any other information you need.
The text was updated successfully, but these errors were encountered: