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

CAPD containers are stopped after a Docker Engine restart #5020

Closed
stmcginnis opened this issue Jul 27, 2021 · 1 comment · Fixed by #5021
Closed

CAPD containers are stopped after a Docker Engine restart #5020

stmcginnis opened this issue Jul 27, 2021 · 1 comment · Fixed by #5021
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@stmcginnis
Copy link
Contributor

User Story

As a user I would like to be able to restart Docker Engine, either via a service restart or a whole system reboot, and have my CAPD based cluster come back after restarting without needing to start the containers manually.

Detailed Description

Docker has a container property called restartPolicy. The default policy is no, which means the container should not be restarted if it is stopped for any reason. I think the most logical policy for CAPD containers is unless-stopped, which would mean containers would always automatically restart unless the user explicitly stopped the container.

https://docs.docker.com/config/containers/start-containers-automatically/#use-a-restart-policy

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 27, 2021
@stmcginnis
Copy link
Contributor Author

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants