You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2019. It is now read-only.
I am not sure if I am able to do this already with the current version, however, it would be super handy to be able to white-list certain defined containers to allow them to avoid being removed from docker in their deployed environments if they have an 'Exited' Docker status...
Use case:
I make use of Data-Only containers which are used to persist data for various other containers to make use of. It also helps in allowing us to move our Data-Only containers from host to host easily as is the point of these.
As Data-Only containers do not need to be running to provide their shared data volumes, they can persist data after events such as reboots/crashes that kill the container.
Here is where Nscale comes in... When Nscale deploys to a target environment, it removes all containers it finds that are 'Exited'. Including Data-Only containers...
Is there a way to prevent the removal of specific containers that exist in the target deployment environment, whether deployed via Nscale or manually? If not, could it be considered as a future enhancement to Nscale?
Many Thanks
Fabio
The text was updated successfully, but these errors were encountered:
Hey,
There is no way to do this at present, however this would be a great enhancement and fairly straightforward to implement I think. Will look into it and let you know. Thanks!
In the meantime I have resorted to simply manually creating the Data-Only container as per Docker Docs, this does not necessarily run the container but merely creates it, thus the container would never have an 'Exited' status. (In hindsight, this is the preferred method for these types of containers, however I believe I would still need to manually create these on each host requiring them)
I do still think it would be an awesome safety feature to white-list containers from any Docker actions performed via Nscale going forward.
Hi Guys
I am not sure if I am able to do this already with the current version, however, it would be super handy to be able to white-list certain defined containers to allow them to avoid being removed from docker in their deployed environments if they have an 'Exited' Docker status...
Use case:
I make use of Data-Only containers which are used to persist data for various other containers to make use of. It also helps in allowing us to move our Data-Only containers from host to host easily as is the point of these.
As Data-Only containers do not need to be running to provide their shared data volumes, they can persist data after events such as reboots/crashes that kill the container.
Here is where Nscale comes in... When Nscale deploys to a target environment, it removes all containers it finds that are 'Exited'. Including Data-Only containers...
Is there a way to prevent the removal of specific containers that exist in the target deployment environment, whether deployed via Nscale or manually? If not, could it be considered as a future enhancement to Nscale?
Many Thanks
Fabio
The text was updated successfully, but these errors were encountered: