Docker Service is stuck on activating, not collaborating..

ptorrezao commented 5 years ago

[x] This is a bug report
[ ] This is a feature request
[x] I searched existing issues before opening this one ** (the existing ones have different outputs)

Expected behaviour

The Docker Service should start

Actual behaviour

The Docker Service is stuck on activating, not collaborating..

Steps to reproduce the behaviour

After the install the docker was working as expected, after the first reboot, the behaviour starts to be a bit funky. Getting stuck on activating the docker service.

This machine is acting like a headless server, so when I plug the keyboard check what is happening and start to do the log in the message "Started bpfilter" appears and i do a docker ps command.

Same steps on via ssh don't trigger the "Started bpfilter".

ptorrezao@armcluster-node01:~$ systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: deactivating (stop-sigterm)
     Docs: https://docs.docker.com
 Main PID: 2490 (dockerd)
    Tasks: 11
   CGroup: /system.slice/docker.service
           └─2490 /usr/bin/dockerd -H unix://

Dec 23 01:08:37 armcluster-node01 systemd[1]: Starting Docker Application Container Engine...
No activity after the previous line

Output of docker version: No Response before the "Started bpfilter" Response after the "Started bpfilter"

Client:
 Version:           18.09.0
 API version:       1.39
 Go version:        go1.10.4
 Git commit:        4d60db4
 Built:             Wed Nov  7 00:52:51 2018
 OS/Arch:           linux/arm64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.0
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.4
  Git commit:       4d60db4
  Built:            Wed Nov  7 00:17:01 2018
  OS/Arch:          linux/arm64
  Experimental:     false

Output of docker info: No Response before the "Started bpfilter" Response after the "Started bpfilter"

docker info
Containers: 2
 Running: 2
 Paused: 0
 Stopped: 0
Images: 2
Server Version: 18.09.0
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 local logentries splunk syslog
Swarm: active
 NodeID: 99tpgoguq59sy26t4hmje4bn7
 Is Manager: true
 ClusterID: qm9sqd33efv5j1ufekqrfvp4s
 Managers: 1
 Nodes: 1
 Default Address Pool: 10.0.0.0/8
 SubnetSize: 24
 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: 192.168.88.25
 Manager Addresses:
  192.168.88.25:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: c4446665cb9c30056f4998ed953e6d4ff22c7c39
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.19.7-aml-s9xxx
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 1.801GiB
Name: armcluster-node01
ID: VPFM:ONND:NNBR:WKC5:REM2:43SJ:FOMW:PDV5:GVYH:6IMD:TWPB:D3DZ
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
Product License: Community Engine

Additional environment details (AWS, VirtualBox, physical, etc.)

This setup is experimental, I'm not a Linux guy but I'm a bit confused. Based on my research the bpfilter stuff is related with the firewall, so may not this issue at all. BUT I'm thinking the service is responsible to lift the networking bridged for docker. But I know nothing.... :)

But the rest of the setup is working as expected... The setup itself is a cheap Android TV with an ArmDebian distro.

ptorrezao@armcluster-node01:~$ uname -r
4.19.7-aml-s9xxx

I saw other similar problems with other software where the software was stuck but I don't have similar configuration file example

dulm commented 4 years ago

same problom with mint 19.3 which based on Ubuntu 18.04.2 LTS.

use docker image centos:centos7

docker run -d \
--name c-cdh6 \
--privileged \
centos:centos7 \
/usr/sbin/init

then display is black(A), but when use vnc viewer login from another computer B, the display is correct on the B.

then in the B's vnc stop the container c-cdh6, and then docker start c-cdh6 will make the A 's display correct again, and appere "Started bpfilter", then login GUI.

if change to

docker run -it \
--name c-cdh6 \
--privileged \
centos:centos7 \
/bin/bash

it start normally.

but when we need systemctl in container, we need to start by /usr/sbin/init.

dulm commented 4 years ago

https://forums.docker.com/t/docker-compose-crashing-xorg-with-every-container/77940

docker / for-linux