On Tue, 2023-08-29 at 15:31 +0100, Peter Humphrey wrote: > > $ cat /var/log/docker.log | cut -d \ -f 2- [to omit date & time] > level=info msg="Starting up" > level=error msg="failed to mount overlay: no such device" > storage-driver=overlay2 > level=error msg="exec: \"fuse-overlayfs\": executable file not found in > $PATH" storage-driver=fuse-overlayfs > level=error msg="Failed to built-in GetDriver graph btrfs /var/lib/docker" > level=info msg="Loading containers: start." > level=warning msg="Could not load necessary modules for IPSEC rules: protocol > not supported" > level=info msg="Default bridge (docker0) is assigned with an IP address > 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address" > level=info msg="Loading containers: done." > level=warning msg="WARNING: No blkio throttle.read_bps_device support" > level=warning msg="WARNING: No blkio throttle.write_bps_device support" > level=warning msg="WARNING: No blkio throttle.read_iops_device support" > level=warning msg="WARNING: No blkio throttle.write_iops_device support" > level=info msg="Docker daemon" > commit=4ffc61430bbe6d3d405bdf357b766bf303ff3cc5 graphdriver=vfs version=24.0.5 > level=info msg="Daemon has completed initialization" > level=info msg="API listen on /var/run/docker.sock" >
Let's start at the top. When you built docker, did you get any feedback from Portage about missing or incorrectly set kernel configuration options? Docker has a strict list of things that it expects to be set (and not set) in your kernel configuration, and portage should let you know what it isn't happy about (at least it did in the past for me before correcting my configs) when you emerge it. Additionally, what USE flags do you have set for app-containers/docker?
