Skip to content
This repository has been archived by the owner on Jan 19, 2018. It is now read-only.

Should the Docker provider remove the deployed containers on failure? #421

Open
cdrage opened this issue Nov 24, 2015 · 7 comments
Open
Assignees

Comments

@cdrage
Copy link
Member

cdrage commented Nov 24, 2015

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?

@dustymabe
Copy link
Contributor

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.

@rtnpro
Copy link
Contributor

rtnpro commented Nov 25, 2015

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.

@rtnpro rtnpro added the GA label Nov 25, 2015
@dustymabe
Copy link
Contributor

@cdrage this is also #319

@rtnpro rtnpro added this to the CDK 2 GA milestone Nov 25, 2015
@rtnpro rtnpro removed the GA label Nov 25, 2015
@dustymabe
Copy link
Contributor

Ok let's get it in for GA then

@rtnpro
Copy link
Contributor

rtnpro commented Dec 15, 2015

This issue should be renamed to Atomic deployments, I think :)

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 Dec 22, 2015
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 11, 2016
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
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
@kadel kadel removed the blocker label Feb 4, 2016
@kadel kadel added blocker and removed blocker labels Feb 4, 2016
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.
rtnpro added a commit to rtnpro/atomicapp that referenced this issue Feb 9, 2016
@rtnpro
Copy link
Contributor

rtnpro commented Feb 9, 2016

Fixed in #456

@rtnpro rtnpro modified the milestone: CDK 2 GA Feb 11, 2016
@dustymabe
Copy link
Contributor

Removing the blocker label from this. We won't be doing this before GA for several reasons.

@dustymabe dustymabe removed the blocker label Feb 11, 2016
@dustymabe dustymabe mentioned this issue Apr 4, 2016
4 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants