Skip to content
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

Dnsmasq not start after reboot or container restart #14

Closed
sergeycherepanov opened this issue Mar 31, 2017 · 2 comments
Closed

Dnsmasq not start after reboot or container restart #14

sergeycherepanov opened this issue Mar 31, 2017 · 2 comments

Comments

@sergeycherepanov
Copy link

sergeycherepanov commented Mar 31, 2017

Hi, I run container with flag --restart always but after reboot the dnsmasq not found in process list. My host machine switched to slave dns server and lose all docker hosts.

To reproduce this issue just do:

docker stop dns-gen
docker start dns-gen
docker top dns-gen #you can see only sh and docker-gen process

I think it's require more flexible process management, something like supervisord but more lightweight, I found alternatives wtiren on Go: https://github.com/codeskyblue/gosuv and http://governator.io/

@sergeycherepanov sergeycherepanov changed the title Dnsmasq not start after reboot ot container restart Dnsmasq not start after reboot or container restart Mar 31, 2017
sergeycherepanov added a commit to djocker/docker-dns-gen that referenced this issue Mar 31, 2017
sergeycherepanov added a commit to djocker/docker-dns-gen that referenced this issue Mar 31, 2017
@sergeycherepanov
Copy link
Author

@jderusse what you think about this?

@jderusse
Copy link
Owner

fixed by #28

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants