-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
Milestone
Comments
Closed
Tentatively scheduling for 0.7. |
This has been implemented in 0.6.5. github.com/dotcloud/docker/blob/v0.6.5/CHANGELOG.md |
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
[18.06] Update swarmkit to 6826639
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
If docker crashes while its child processes were running, it should be capable of seamlessly restoring its previous state when run again.
This means:
Re-attaching to child processes which are still running (or killing them if that's not possible)
Re-starting processes which were running at the time of the crash (eg. after a host reboot).
The text was updated successfully, but these errors were encountered: