Docker service on a node can reload config only twice
See original GitHub issueWhen try to reload config of docker (without restart) on a Codenvy node more then two times changes are ignored.
Reproduction Steps:
- Run
docker info
and remember existing labels (if no labels configured section is not appeared) - Edit / create file
/etc/docker/daemon.json
and add a new label. Example of content of created file:{"labels":["com.codenvy.some-label=somevalue"]}
- Reload docker config. Do NOT restart docker, use sighup signal:
kill -SIGHUP $(<"/var/run/docker.pid")
Usedocker info
to ensure, that the label is present. - Change label value and reload config again. Check again, that changes are applied.
- Change label value again and again reload config (3rd time).
Expected behavior: Config should be reloaded again and next times.
Observed behavior: Nothing changes. Config is left as after second reloading. To apply new changes docker restart is needed.
Codenvy version: 5.0.0-M8-SNAPSHOT OS and version: CentOS Linux 7 (Core) 3.10.0-327.10.1.el7.x86_64 Docker version: Version: 1.11.1 API version: 1.23 Swarm: Server Version: swarm/1.2.3
Additional information:
Problem only started happening recently, didn’t happen in an older version of Codenvy: Yes Problem can be reliably reproduced: Yes
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Keep containers alive during daemon downtime
There are two ways to enable the live restore setting to keep containers alive when the daemon becomes unavailable. Only do one of...
Read more >Deploy services to a swarm - Docker Documentation
First, create overlay network on a manager node using the docker network create command with the --driver overlay flag. After you create an...
Read more >docker service create - Docker Documentation
Create a service with a config. The config will be mounted into redis-config , be owned by the user who runs the command...
Read more >Docker daemon configuration overview
To configure the Docker daemon using a JSON file, create a file at /etc/docker/daemon. json on Linux systems, or C:\ProgramData\docker\config\daemon. json on ...
Read more >docker service update - Docker Documentation
For example, only changing the --update-parallelism setting will not ... be used to perform a rolling restart without any changes to the service...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Issue in docker is resolved, fix is merged for 1.14.0 milestone.
This problem occurs when docker on a node is started with
cluster-store
andcluster-advertise
options. Otherwise everything works fine. In case, when onlycluster-store
is set, docker hungs up on 3rd config reload. Logs: after 1st SIGHUP:2nd:
3rd: