Electric Eel RC1 fails to start Docker

Just did a fresh install of EE RC1. Tried to setup some apps, but Docker fails to start with the following error:
failed to start daemon: Error initializing network controller: error creating default "bridge" network: all predefined address pools have been fully subnetted

root@truenas[/home/truenas_admin]# service docker start
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
root@truenas[/home/truenas_admin]# journalctl -xeu docker.service
β–‘β–‘ The job identifier is 3040.
Oct 03 12:19:25 truenas dockerd[18676]: time="2024-10-03T12:19:25.534949274+03:00" level=info msg="Starting up"
Oct 03 12:19:25 truenas dockerd[18676]: time="2024-10-03T12:19:25.564676511+03:00" level=info msg="[graphdriver] trying configured driver: overlay2"
Oct 03 12:19:25 truenas dockerd[18676]: time="2024-10-03T12:19:25.619421735+03:00" level=info msg="Loading containers: start."
Oct 03 12:19:27 truenas dockerd[18676]: time="2024-10-03T12:19:27.476310632+03:00" level=info msg="stopping event stream following graceful shutdown" error="<nil>" module=libcontainerd namespace=moby
Oct 03 12:19:27 truenas dockerd[18676]: failed to start daemon: Error initializing network controller: error creating default "bridge" network: all predefined address pools have been fully subnetted
Oct 03 12:19:27 truenas systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
β–‘β–‘ Subject: Unit process exited
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://www.debian.org/support
β–‘β–‘ 
β–‘β–‘ An ExecStart= process belonging to unit docker.service has exited.
β–‘β–‘ 
β–‘β–‘ The process' exit code is 'exited' and its exit status is 1.
Oct 03 12:19:27 truenas systemd[1]: docker.service: Failed with result 'exit-code'.
β–‘β–‘ Subject: Unit failed
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://www.debian.org/support
β–‘β–‘ 
β–‘β–‘ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Oct 03 12:19:27 truenas systemd[1]: Failed to start docker.service - Docker Application Container Engine.
β–‘β–‘ Subject: A start job for unit docker.service has failed
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://www.debian.org/support
β–‘β–‘ 
β–‘β–‘ A start job for unit docker.service has finished with a failure.
β–‘β–‘ 
β–‘β–‘ The job identifier is 3040 and the job result is failed.
Oct 03 12:19:27 truenas systemd[1]: docker.service: Consumed 1.158s CPU time.
β–‘β–‘ Subject: Resources consumed by unit runtime
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://www.debian.org/support
β–‘β–‘ 
β–‘β–‘ The unit docker.service completed and consumed the indicated resources.
Oct 03 12:19:29 truenas systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
β–‘β–‘ Subject: Automatic restarting of a unit has been scheduled
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://www.debian.org/support
β–‘β–‘ 
β–‘β–‘ Automatic restarting of the unit docker.service has been scheduled, as the result for
β–‘β–‘ the configured Restart= setting for the unit.
Oct 03 12:19:29 truenas systemd[1]: Stopped docker.service - Docker Application Container Engine.
β–‘β–‘ Subject: A stop job for unit docker.service has finished
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://www.debian.org/support
β–‘β–‘ 
β–‘β–‘ A stop job for unit docker.service has finished.
β–‘β–‘ 
β–‘β–‘ The job identifier is 3112 and the job result is done.
Oct 03 12:19:29 truenas systemd[1]: docker.service: Consumed 1.158s CPU time.
β–‘β–‘ Subject: Resources consumed by unit runtime
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://www.debian.org/support
β–‘β–‘ 
β–‘β–‘ The unit docker.service completed and consumed the indicated resources.
Oct 03 12:19:29 truenas systemd[1]: docker.service: Start request repeated too quickly.
Oct 03 12:19:29 truenas systemd[1]: docker.service: Failed with result 'exit-code'.
β–‘β–‘ Subject: Unit failed
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://www.debian.org/support
β–‘β–‘ 
β–‘β–‘ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Oct 03 12:19:29 truenas systemd[1]: Failed to start docker.service - Docker Application Container Engine.
β–‘β–‘ Subject: A start job for unit docker.service has failed
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://www.debian.org/support
β–‘β–‘ 
β–‘β–‘ A start job for unit docker.service has finished with a failure.
β–‘β–‘ 
β–‘β–‘ The job identifier is 3112 and the job result is failed

/etc/docker/daemon.json

{"data-root": "/mnt/.ix-apps/docker", "exec-opts": ["native.cgroupdriver=cgroupfs"], "iptables": true, "storage-driver": "overlay2", "default-address-pools": [{"base": "172.30.0.0/16", "size": 27}, {"base": "172.31.0.0/16", "size": 27}]}

Anyone else getting this? Ideas how to fix this?

Try this:
midclt call -job docker.update '{"address_pools": [{"base": "172.17.0.0/12", "size": 24}]}'

Per NAS-131538

2 Likes

Thanks! That worked! :bowing_man:

You’re amazing