when deploying this service, if the container is already running, it does not get redeployed.
workaround: deploy a specific tag-by-hash to ensure the correct container is running/deployed.
there is probably another way to ensure that the container is redeployed when the playbook is run.
when deploying this service, if the container is already running, it does not get redeployed.
workaround: deploy a specific tag-by-hash to ensure the correct container is running/deployed.
there is probably another way to ensure that the container is redeployed when the playbook is run.