View previous topic :: View next topic |
Author |
Message |
lcsavb n00b
Joined: 11 Jun 2020 Posts: 46 Location: Sao Paulo / Brasil
|
Posted: Mon Aug 17, 2020 12:40 pm Post subject: Docker service crashes on startup |
|
|
Hi,
I'm not able to start the docker service.
My kernel version is 5.6.19 and I'm running Gentoo on a ZFS root.
The output of dmesg | grep docker is:
Code: | [ 9.633157] overlayfs: filesystem on '/var/lib/docker/overlay2/check-overlayfs-support335667479/upper' not supported as upperdir |
Code: | [contrib] ./check-config.sh
info: reading kernel config from /proc/config.gz ...
Generally Necessary:
- cgroup hierarchy: properly mounted [/sys/fs/cgroup]
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_CPUSETS: enabled
- CONFIG_MEMCG: enabled
- CONFIG_KEYS: enabled
- CONFIG_VETH: enabled
- CONFIG_BRIDGE: enabled
- CONFIG_BRIDGE_NETFILTER: enabled
- CONFIG_NF_NAT_IPV4: missing
- CONFIG_IP_NF_FILTER: enabled
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled
- CONFIG_NETFILTER_XT_MATCH_IPVS: enabled
- CONFIG_IP_NF_NAT: enabled (as module)
- CONFIG_NF_NAT: enabled
- CONFIG_NF_NAT_NEEDED: missing
- CONFIG_POSIX_MQUEUE: enabled
Optional Features:
- CONFIG_USER_NS: enabled
- CONFIG_SECCOMP: enabled
- CONFIG_CGROUP_PIDS: enabled
- CONFIG_MEMCG_SWAP: enabled
- CONFIG_MEMCG_SWAP_ENABLED: enabled
(cgroup swap accounting is currently enabled)
- CONFIG_BLK_CGROUP: enabled
- CONFIG_BLK_DEV_THROTTLING: enabled
- CONFIG_IOSCHED_CFQ: missing
- CONFIG_CFQ_GROUP_IOSCHED: missing
- CONFIG_CGROUP_PERF: enabled
- CONFIG_CGROUP_HUGETLB: enabled
- CONFIG_NET_CLS_CGROUP: enabled
- CONFIG_CGROUP_NET_PRIO: enabled
- CONFIG_CFS_BANDWIDTH: enabled
- CONFIG_FAIR_GROUP_SCHED: enabled
- CONFIG_RT_GROUP_SCHED: enabled
- CONFIG_IP_NF_TARGET_REDIRECT: missing
- CONFIG_IP_VS: enabled
- CONFIG_IP_VS_NFCT: enabled
- CONFIG_IP_VS_PROTO_TCP: enabled
- CONFIG_IP_VS_PROTO_UDP: enabled
- CONFIG_IP_VS_RR: enabled
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
- Network Drivers:
- "overlay":
- CONFIG_VXLAN: enabled
Optional (for encrypted networks):
- CONFIG_CRYPTO: enabled
- CONFIG_CRYPTO_AEAD: enabled
- CONFIG_CRYPTO_GCM: enabled (as module)
- CONFIG_CRYPTO_SEQIV: enabled (as module)
- CONFIG_CRYPTO_GHASH: enabled (as module)
- CONFIG_XFRM: enabled
- CONFIG_XFRM_USER: enabled
- CONFIG_XFRM_ALGO: enabled
- CONFIG_INET_ESP: missing
- CONFIG_INET_XFRM_MODE_TRANSPORT: missing
- "ipvlan":
- CONFIG_IPVLAN: enabled
- "macvlan":
- CONFIG_MACVLAN: enabled
- CONFIG_DUMMY: enabled
- "ftp,tftp client in container":
- CONFIG_NF_NAT_FTP: enabled
- CONFIG_NF_CONNTRACK_FTP: enabled
- CONFIG_NF_NAT_TFTP: missing
- CONFIG_NF_CONNTRACK_TFTP: missing
- Storage Drivers:
- "aufs":
- CONFIG_AUFS_FS: missing
- "btrfs":
- CONFIG_BTRFS_FS: enabled
- CONFIG_BTRFS_FS_POSIX_ACL: enabled
- "devicemapper":
- CONFIG_BLK_DEV_DM: enabled
- CONFIG_DM_THIN_PROVISIONING: enabled
- "overlay":
- CONFIG_OVERLAY_FS: enabled
- "zfs":
- /dev/zfs: present
- zfs command: available
- zpool command: available
Limits:
- /proc/sys/kernel/keys/root_maxkeys: 1000000
|
equery u docker
Code: |
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for app-emulation/docker-19.03.12:
U I
- - apparmor : Enable AppArmor support.
- - aufs : Enables dependencies for the "aufs" graph driver,
including necessary kernel flags.
+ + btrfs : Enables dependencies for the "btrfs" graph driver,
including necessary kernel flags.
+ + container-init : Makes the a staticly-linked init system tini available
inside a container.
+ + device-mapper : Enables dependencies for the "devicemapper" graph
driver, including necessary kernel flags.
- - hardened : Activate default security enhancements for toolchain
(gcc, glibc, binutils)
+ + overlay : Enables dependencies for the "overlay" graph driver,
including necessary kernel flags.
+ + seccomp : Enable seccomp (secure computing mode) to perform system
call filtering at runtime to increase security of
programs
|
Ideas on what configuration is wrong? Thanks!
Should I use zfs as overlay as described in https://docs.docker.com/storage/storagedriver/zfs-driver/? |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21791
|
Posted: Mon Aug 17, 2020 8:08 pm Post subject: |
|
|
Your subject line says that Docker crashes on startup, but your post body makes no mention of any crash. The dmesg output may just be a general diagnostic, and not actually fatal. What do you see that makes you think Docker crashed? |
|
Back to top |
|
|
lcsavb n00b
Joined: 11 Jun 2020 Posts: 46 Location: Sao Paulo / Brasil
|
Posted: Mon Aug 17, 2020 8:28 pm Post subject: |
|
|
Code: |
Runlevel: default
zfs-zed [ started ]
sysklogd [ started ]
cronie [ started ]
docker [ crashed ]
NetworkManager [ started ]
libvirtd [ started ]
lm_sensors [ started ]
netmount [ started ]
xdm [ started ]
zfs-share [ started ]
local
|
|
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21791
|
Posted: Mon Aug 17, 2020 10:21 pm Post subject: |
|
|
That indicates the Docker daemon is no longer running as the pid that the service manager expected. You need to find the message(s) it wrote before terminating to see why it is not running. |
|
Back to top |
|
|
|