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
We updated to newer docker-engine version and executed puppet agent -t on the host. The docker-engine was upgraded and restarted, then a mix of green and red for container restarts. On inspection, the depends listing was being ignored.
We restarted the hosted and each container was correctly listed in docker ps. The containers with declared dependencies have a correct init.d script.
Is it possible that when puppet executed and upgrades, puppet is holding itself responsible for starting those containers and ignoring the depends specified?
The text was updated successfully, but these errors were encountered:
Module version: 5.0.
We updated to newer
docker-engine
version and executedpuppet agent -t
on the host. Thedocker-engine
was upgraded and restarted, then a mix of green and red for container restarts. On inspection, thedepends
listing was being ignored.We restarted the hosted and each container was correctly listed in
docker ps
. The containers with declared dependencies have a correctinit.d
script.Is it possible that when puppet executed and upgrades, puppet is holding itself responsible for starting those containers and ignoring the
depends
specified?The text was updated successfully, but these errors were encountered: