Docker Community Forums

Share and learn in the Docker community.

Troubleshooting swarm service create


(Dlsmlss) #1

Got some strange error during creating service better to see it in gif:


and those steps repeats again and again.
If stop this task:

[dlsmlss@mss-docker00 ~]$ docker service create --name busybox01 busybox
ok2yf5xglqf8ti7oshrs75egv
overall progress: 0 out of 1 tasks
1/1: starting [============================================> ]
verify: Detected task failure
^COperation continuing in background.
Use docker service ps ok2yf5xglqf8ti7oshrs75egv to check progress.
[dlsmlss@mss-docker00 ~]$ docker service ps ok2yf5xglqf8ti7oshrs75egv
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
sswovllbk3ve busybox01.1 busybox:latest mss-docker00.sodrugestvo.local Ready Ready less than a second ago
xu9pznwbxdnr _ busybox01.1 busybox:latest mss-docker00.sodrugestvo.local Shutdown Complete 14 seconds ago
z684l4e0f4rp _ busybox01.1 busybox:latest mss-docker00.sodrugestvo.local Shutdown Complete about a minute ago
xvqil7vygjye _ busybox01.1 busybox:latest mss-docker00.sodrugestvo.local Shutdown Complete 2 minutes ago
zeaafk4ng67c _ busybox01.1 busybox:latest mss-docker00.sodrugestvo.local Shutdown Complete 2 minutes ago

If just run this:

[dlsmlss@mss-docker00 ~]$ docker inspect --format “{{.Status.Err}}” $(docker service ps busybox01 | awk ‘{print $1}’ | head -n 3 | tail -n 1)

[dlsmlss@mss-docker00 ~]$

There is nothing to take a look at :frowning:

[dlsmlss@mss-docker00 ~]$ docker -v
Docker version 18.06.0-ce, build 0ffa825
[dlsmlss@mss-docker00 ~]$ docker info
Containers: 79
Running: 2
Paused: 0
Stopped: 77
Images: 6
Server Version: 18.06.0-ce
Storage Driver: overlay2
Backing Filesystem: xfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: active
NodeID: yj807awgi1j3kbqwgf4cnab0k
Is Manager: true
ClusterID: zm0h8k4yyf9wkwr2xlreq1uab
Managers: 1
Nodes: 1
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: 172.21.171.15
Manager Addresses:
172.21.171.15:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: d64c661f1d51c48782c9cec8fda7604785f93587
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 3.10.0-862.9.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.702GiB
Name: mss-docker00.sodrugestvo.local
ID: S77A:WBER:ODTY:74IZ:DX7L:C2CU:QG6F:YR5P:GJN7:ZOJL:CRBC:65TF
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

If i just try to run this not as service it works perfect:

[dlsmlss@mss-docker00 ~]$ docker run -it --rm --name busybox_run busybox /bin/sh
/ # busybox | head -1
BusyBox v1.29.1 (2018-07-16 19:39:33 UTC) multi-call binary.
/ # [dlsmlss@mss-docker00 ~]$


(Hemingway19) #2

I’m facing the same issue.
This is happening for standard images as well.

docker service create --name test–replicas=3 ubuntu:16.04
x6ndzz3bx07qbp2hm88kvfjl8
overall progress: 0 out of 3 tasks
1/3: preparing [=================================> ]
2/3: preparing [=================================> ]
3/3: preparing [=================================> ]
verify: Detected task failure
(ctrl+c)Operation continuing in background.
Use docker service ps x6ndzz3bx07qbp2hm88kvfjl8 to check progress

Thought it might have been due to apt-get update, but doesn’t seem to be the case.
I’ve reinstalled docker (uninstalled/purged/removed all possible packages/files), but the issue persists.

Hoping to hear for the community asap.