Open viktor-thell-seal opened 4 years ago
Observed with non-forced update as well, which seems more problematic.
docker version
Client: Docker Engine - Community
Version: 26.1.1
API version: 1.45
Go version: go1.21.9
Git commit: 4cf5afa
Built: Tue Apr 30 11:47:53 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 26.1.1
API version: 1.45 (minimum version 1.24)
Go version: go1.21.9
Git commit: ac2de55
Built: Tue Apr 30 11:47:53 2024
OS/Arch: linux/amd64
Experimental: true
containerd:
Version: 1.6.31
GitCommit: e377cd56a71523140ca6ae87e30244719194a521
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Expected behavior
A forced update of a service should not change the mount order.
Actual behavior
When running a forced update of a service to restart it the order of the mounts change, this causes unexpected service restarts when re-deploying the stack.
Steps to reproduce the behavior
Using this compose-file:
One can now see that three tasks has been created, although the last deploy should not have resulted in a new task as nothing changed from the first deploy.
When comparing the output of docker inspect for the first and the second task one can see that the mounts have changed order:
However, when comparing the output of docker inspect for the first and the third task one can see that the mounts are back in order:
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.) Physical machine