Docker swarm init - network docker_gwbridge not creating

Docker Engine Swarm
1

  1. docker swarm init - unable to create docker_gwbridge network in ubuntu 16.04

  2. In syslog error says - Failed creating ingress network: container ingress-sbox is already present in sandbox ingress_sbox

  3. why this two warnings in docker info - No cpu cfs quota support, No cpu cfs period support

docker info

Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 2
Server Version: 18.01.0-ce
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 macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: active
NodeID: vll17lcydq885j4tw15hgu79d
Is Manager: true
ClusterID: koei51fo0gxzgj4ijkzn7gn22
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: 3
Dispatcher:
Heartbeat Period: 5 seconds
CA Configuration:
Expiry Duration: 3 months
Force Rotate: 0
Autolock Managers: false
Root Rotation In Progress: false
Node Address: 192.99.192.20
Manager Addresses:
192.99.192.20:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 89623f28b87a6004d4b785663257362d1658a729
runc version: b2567b37d7b75eb4cf325b77297b140ea686ce8f
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 4.9.77-xxxx-std-ipv6-64
Operating System: Ubuntu 16.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 62.94GiB
Name: node1
ID: 4FU7:TOSD:23BL:X5CI:KFZP:GQHH:EYXA:E2SY:L3WC:47XG:J45X:GBEQ
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

WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support

2

Having the exact same problem. Did you manage to solve this?

3

On Centos7 I solved this problem simply restarting the docker demon with systemctl restart docker
Hope this help.