Description
Hi!
It looks like command docker service create ignores --update-order parameter.
Steps to reproduce the issue:
- Run in docker swarm cluster
docker service create --update-order start-first --restart-condition none --no-healthcheck --name start-first-test alpine tail -f /dev/null
- Check output of
docker inspect start-first-test --format '{{ json .Spec.UpdateConfig.Order }}'
Describe the results you received:
root@test-manager-01:~# docker service create --update-order start-first --restart-condition none --no-healthcheck --name start-first-test alpine tail -f /dev/null
cnx2j810zwcge4l2211u7meqy
overall progress: 1 out of 1 tasks
1/1: running [==================================================>]
verify: Service converged
root@test-manager-01:~# docker inspect start-first-test --format '{{ json .Spec.UpdateConfig.Order }}'
"stop-first"
Describe the results you expected:
UpdateConfig.Order of a new service should be "start-first"
Output of docker version:
Client: Docker Engine - Community
Version: 19.03.13
API version: 1.40
Go version: go1.13.15
Git commit: 4484c46d9d
Built: Wed Sep 16 17:03:03 2020
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.13
API version: 1.40 (minimum version 1.12)
Go version: go1.13.15
Git commit: 4484c46d9d
Built: Wed Sep 16 17:01:33 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.3.7
GitCommit: 8fba4e9a7d01810a393d5d25a3621dc101981175
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
Output of docker info:
Client:
Debug Mode: false
Server:
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 1
Server Version: 19.03.13
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: active
NodeID: v2ob63wvh06t2xa30snjpekj5
Is Manager: true
ClusterID: jwow2iuh7j72bot1mgucrt6va
Managers: 1
Nodes: 1
Default Address Pool: 10.0.0.0/8
SubnetSize: 24
Data Path Port: 4789
Orchestration:
Task History Retention Limit: 5
Raft:
Snapshot Interval: 10000
Number of Old Snapshots to Retain: 0
Heartbeat Tick: 1
Election Tick: 10
Dispatcher:
Heartbeat Period: 5 seconds
CA Configuration:
Expiry Duration: 3 months
Force Rotate: 0
Autolock Managers: false
Root Rotation In Progress: false
Node Address: 10.128.0.15
Manager Addresses:
10.128.0.15:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 8fba4e9a7d01810a393d5d25a3621dc101981175
runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.19.0-0.bpo.8-amd64
Operating System: Debian GNU/Linux 9 (stretch)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.948GiB
Name: test-manager-01
ID: EXYO:YTB2:VJ2I:BF3D:ON6N:AGPV:HBS7:QGFT:VBYF:GZMK:X3NH:GVX6
Docker Root Dir: /var/lib/docker
Debug Mode: true
File Descriptors: 41
Goroutines: 155
System Time: 2020-10-23T08:08:12.87835291Z
EventsListeners: 1
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
Description
Hi!
It looks like command
docker service createignores --update-order parameter.Steps to reproduce the issue:
docker service create --update-order start-first --restart-condition none --no-healthcheck --name start-first-test alpine tail -f /dev/nulldocker inspect start-first-test --format '{{ json .Spec.UpdateConfig.Order }}'Describe the results you received:
Describe the results you expected:
UpdateConfig.Orderof a new service should be "start-first"Output of
docker version:Output of
docker info: