-
-
Notifications
You must be signed in to change notification settings - Fork 792
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
Updated docker upstart script (should fix service docker restart). #173
Updated docker upstart script (should fix service docker restart). #173
Conversation
Fixed spec to make travis happy (sorry forgot about the spec after changing the template). |
Feel free to squash the 3 commits of this PR before merging. |
Edit: In fact the error below is from running without including PR #173. When I do run from @jperville's code it seems to be fixed. I just tested this via test-kitchen, including the default recipe with this wrapper recipe:
Unfortunately it doesn't seem to resolve the issue for me, as the default recipe is still failing to converge on 14.04:
|
@bplunkert I am using the lxc-docker package, not the ubuntu docker.io package (try to set node['docker']['package']['name'] = 'lxc-docker' in your wrapper cookbook just after setting repo_url; see #171 for details). |
@jperville Sorry. I think I may have been mixed up -- it looks like this PR fixes this issue for me, both with and without lxc-docker. I wasn't testing the right fork :) So anyway it looks good to me! 👍 |
Thanks both of you for testing this out. Will merge and release in next bugfix version shortly. |
Updated docker upstart script (should fix service docker restart).
This PR updates the template for the upstart service in `/etc/init/docker.conf to match the upstream version.
The story: I was wondering why my docker containers poofed each time I ran
service docker restart
. Before this PR, typingsudo service docker restart
would immediately restart the daemon but the containers are gone indocker ps
. The reason is that upstart did not detect the end of docker daemon (tracking the pid of the shell wrapper) so it would not emit the "started" event and the container services would not be stopped cleanly nor restarted cleanly.After this PR, running
sudo service docker restart
with containers are running should take a little longer, while docker shuts down the running containers gracefully.