This repository has been archived by the owner on Jan 19, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 71
Should the Docker provider remove the deployed containers on failure? #421
Labels
Comments
we will be adding some tooling around "removing" containers sometime soon as part of #308 .. Let's revisit after we have the full lifecyle in place.. We may decide that if a part of it fails then it is reasonable to have the user do a clean or equivalent before they start to run it again. |
It's a generic problem, and not just for Docker. As we had already discussed in the past, IIRC, deployments should be atomic. If the deployment of a component fails, we should rollback the deployment of any other deployed component. |
Ok let's get it in for GA then |
This issue should be renamed to |
rtnpro
added a commit
to rtnpro/atomicapp
that referenced
this issue
Dec 15, 2015
…tomic#421 When there's an error during running a Nulecule application, rollback the changes made by stopping the application.
rtnpro
added a commit
to rtnpro/atomicapp
that referenced
this issue
Dec 21, 2015
…tomic#421 When there's an error during running a Nulecule application, rollback the changes made by stopping the application.
rtnpro
added a commit
to rtnpro/atomicapp
that referenced
this issue
Dec 22, 2015
…tomic#421 When there's an error during running a Nulecule application, rollback the changes made by stopping the application.
rtnpro
added a commit
to rtnpro/atomicapp
that referenced
this issue
Jan 11, 2016
…tomic#421 When there's an error during running a Nulecule application, rollback the changes made by stopping the application.
rtnpro
added a commit
to rtnpro/atomicapp
that referenced
this issue
Jan 19, 2016
…tomic#421 When there's an error during running a Nulecule application, rollback the changes made by stopping the application.
rtnpro
added a commit
to rtnpro/atomicapp
that referenced
this issue
Jan 19, 2016
…tomic#421 When there's an error during running a Nulecule application, rollback the changes made by stopping the application.
rtnpro
added a commit
to rtnpro/atomicapp
that referenced
this issue
Feb 9, 2016
…tomic#421 When there's an error during running a Nulecule application, rollback the changes made by stopping the application.
Fixed in #456 |
Removing the blocker label from this. We won't be doing this before GA for several reasons.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When deploying using the Docker provider, you may run into the issues of a container already being deployed on a current port.
Unfortunatley, even if it fails, the containers you deployed up until that point are lingering on.
Should the Docker provider go through all the deployed containers thus far and remove them? Or is this too dangerous?
The text was updated successfully, but these errors were encountered: