WARN Running iptables -wait -t nat -L -n failed with message: `iptables v1.8.7 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.`, error: exit status 3 INFO stopping event stream following graceful shutdown error="" module=libcontainerd namespace=moby INFO stopping event stream following graceful shutdown error="context canceled" module=libcontainerd namespace=plugins. start-stop-daemon -start -background -no-close -exec /usr/bin/dockerd -pidfile /var/run/docker-ssd.pid -make-pidfile -p /var/run/docker.pid INFOT10:48:18.439327900+09:00 Starting up INFOT10:48:18.449106100+09:00 libcontainerd: started new containerd process pid9465 INFOT10:48:18.449389900+09:00. Also, maybe due to the process id you are trying to preserve is. Your antivirus might have deleted monerod.exe file or the firewall is stopping daemon from accessing the network. INFO Starting up INFO libcontainerd: started new containerd process pid=9465 INFO parsed scheme: "unix" module=grpc INFO scheme "unix" not registered, fallback to default scheme module=grpc INFO ccResolverWrapper: sending update to cc: module=grpc INFO ClientConn switching balancer to "pick_first" module=grpc INFO using prior storage driver: overlay2 WARN Your kernel does not support cgroup memory limit WARN Unable to find cpu cgroup in mounts WARN Unable to find blkio cgroup in mounts WARN Unable to find cpuset cgroup in mounts WARN Unable to find pids cgroup in mounts INFO Loading containers: start. This error comes from being unable to restart the ADB-server or unable to kill all processes. There are 2 reasons why daemon fails to start. However, I believe such change won't be persistent over reboot, thus need a permanent solution.# start-stop-daemon -start -background -no-close -exec /usr/bin/dockerd -pidfile /var/run/docker-ssd.pid -make-pidfile -p /var/run/docker.pid What I found works is: ip link add name docker0 type bridge Try updating the kernel: sudo apt update sudo apt dist-upgrade If that doesnt work, try uninstalling/reinstalling snap: Find installed snaps: snap list If. Nov 23 21:56:08 myhost dockerd: failed to start daemon: Error initializing network controller: list bridge addresses failed: PredefinedLocalScopeDefaultNetworks List: : no available networkĪnd I've found out the reason is that there is no -bip flag any more to docker: /usr/bin/docker daemon -debug -bip=192.168.0.0/20
Exacactly the same issue as Failed to start Docker Container Engine, as I'm getting dockerd failed to start daemon: Error initializing network controller: list bridge addresses failed: PredefinedLocalScopeDefaultNetworks List no available network: $ journalctl -xeu rvice | grep 'failed to start daemon'
0 kommentar(er)
