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

Restore after a crash #27

Closed
shykes opened this issue Mar 9, 2013 · 2 comments
Closed

Restore after a crash #27

shykes opened this issue Mar 9, 2013 · 2 comments
Milestone

Comments

@shykes
Copy link
Contributor

shykes commented Mar 9, 2013

If docker crashes while its child processes were running, it should be capable of seamlessly restoring its previous state when run again.

This means:

  1. Re-attaching to child processes which are still running (or killing them if that's not possible)

  2. Re-starting processes which were running at the time of the crash (eg. after a host reboot).

@shykes
Copy link
Contributor Author

shykes commented Aug 24, 2013

Tentatively scheduling for 0.7.

@shykes
Copy link
Contributor Author

shykes commented Nov 11, 2013

This has been implemented in 0.6.5. github.com/dotcloud/docker/blob/v0.6.5/CHANGELOG.md

@shykes shykes closed this as completed Nov 11, 2013
crosbymichael referenced this issue in crosbymichael/docker Nov 14, 2013
crosbymichael pushed a commit that referenced this issue Aug 6, 2014
Update hack/vendor.sh to use libcontainer's update-vendor.sh script as the source of truth for libcontainer deps and not include them in Docker's repo twice
tiborvass pushed a commit to tiborvass/docker that referenced this issue Jul 20, 2018
ndeloof added a commit to ndeloof/docker that referenced this issue Jul 28, 2022
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

1 participant