-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Docker Manager came up with the need to run docker in standalone mode with options that swarm cluster service was not possible or extremely impractical.
In some environments we have the need to create several applications docker (apache, traefik, tomcat, jboss, wildfly, php) and to access some properties of these servers it is necessary to access them by ip:port. But since there are many, it is impracticable to publish the port in each service in swarm and use them only in stadand alone mode we lose high availability property of the swarm cluster.
Docker-manager comes to help with this. It is created as a service in swarm and runs and controls N dockers configured in docker-manager.cfg in standalone mode.
So if the docker host drops or the service migrates for some reason, dockers managed by docker-manager are disconnected and started on the new host that the service is instantiated.
Docker-manager will run the dockers with the implicit option (--rm) and some control labels, unless specified with the --restart option. He keeps track of these docker, and if any one falls, it starts again.
If the service migrates or for some reason the docker-manager is not running, another docker(manager-gc) that was implicitly started in standalone mode turns off all dockers created by docker-manager and then hangs up.