Open ghost opened 4 years ago
@xupyp1 can you provide the commands you ran to get the error?
We usually use the command docker service update --detach --force --update-failure-action=rollback --with-registry-auth --image=$IMAGE --config-rm OLD --config-add NEW $SERVICENAME
Last command was: docker service update --detach --force --update-failure-action=rollback --with-registry-auth --image=REDACTED --config-rm REDACTED.00000002 --config-add source=REDACTED.properties.00000002,target=REDACTED --config-rm REDACTED.00000007 --config-add source=REDACTED.00000007,target=REDACTED --config-rm REDACTED.00000026 --config-add source=REDACTED.00000026,target=REDACTED --update-parallelism=1 --update-delay=60s REDACTED
Expected behavior
docker swarm will update the service I will get text in
docker service ps SERVICE
in column CURRENT STATE "Running 2 minutes ago"Actual behavior
Sometimes i get an error: "Failed 22 minutes ago "starting container failed: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:432: running prestart hook 0 caused \\"error running hook: exit status 1, stdout: , stderr: time=\\\\"2019-11-12T19:09:09+07:00\\\\" level=fatal msg=\\\\"failed to add interface veth44d4290 to sandbox: failed to set link up: device or resource busy\\\\"\\n\\"\"": unknown"" Sometimes everything goes fine
Steps to reproduce the behavior
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.) Selfhosted VM on KVM Debian 9 Networking driver - macvlan