we use the docker/sdk for office-internal stage environments which run on local hardware. But these hardware/servers are for example restarted occasionally or are reconfigured automatically so it would be great to set a restart-policy for the containers to restart them after the server (and docker) came up after a restart.
This could maybe configured as a deploy-file-wide parameter which automatically reflects to al relevant containers (yves, zed, gateway, db, ...)
Could you please describe why would you like to have a restart policy for containers? What do you want to achieve with that? Do you have a case/problem you are trying to solve with this solution? I want to understand better your case.
Hello Dmytro,
we use the docker/sdk for office-internal stage environments which run on local hardware. But these hardware/servers are for example restarted occasionally or are reconfigured automatically so it would be great to set a restart-policy for the containers to restart them after the server (and docker) came up after a restart.
This could maybe configured as a deploy-file-wide parameter which automatically reflects to al relevant containers (yves, zed, gateway, db, ...)
Hi Sebastian,
Could you please describe why would you like to have a restart policy for containers? What do you want to achieve with that? Do you have a case/problem you are trying to solve with this solution?
I want to understand better your case.
Thank you. Dmytro
Hi Sebastian,
Thank you for your idea 👍
- Jeremy Fourna