Docker Not Starting

[fleamour]

Sep 09 00:31:01 G41M-COMBO systemd[1]: Failed to start Docker Application Container Engine.
Sep 09 00:31:01 G41M-COMBO systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Sep 09 00:31:01 G41M-COMBO systemd[1]: docker.service: Start request repeated too quickly.
Sep 09 00:31:01 G41M-COMBO systemd[1]: docker.service: Failed with result 'start-limit-hit'.
Sep 09 00:31:01 G41M-COMBO systemd[1]: Failed to start Docker Application Container Engine.

Discreet Nvidia 2024 & trying to run WinBoat. Ancient C2D Extreme chipset.

[deano_ferrari]

That’s just the symptoms. Examine

sudo journalctl -u docker.service -b --no-pager

[deano_ferrari]

BTW, did it happen after a zypper dup?

Maybe also show

rpm -q docker docker-compose
zypper se -si docker

[deano_ferrari]

System/CPU information might be relevant here because you mentioned you’re using an older Core 2 Extreme system? Might be an issue with trying to run KVM/WinBoat?
inxi -SMaz

[fleamour]

Firewalld:

Sep 09 00:22:38 G41M-COMBO systemd[1]: Starting Docker Application Container Engine...
Sep 09 00:22:41 G41M-COMBO dockerd[7090]: time="2026-09-09T00:22:41.795096933+01:00" level=warning msg="Failed to clean firewalld rules for bridge network" error="firewalld: interface \"docker0\" not found in docker zone"
Sep 09 00:22:42 G41M-COMBO dockerd[7090]: failed to start daemon: Error initializing network controller: error creating default "bridge" network: ZONE_CONFLICT: 'docker0' already bound to 'public'
Sep 09 00:22:42 G41M-COMBO systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Sep 09 00:22:42 G41M-COMBO systemd[1]: docker.service: Failed with result 'exit-code'.
Sep 09 00:22:42 G41M-COMBO systemd[1]: Failed to start Docker Application Container Engine.

[deano_ferrari]

Ok, so Docker is trying to create/manage its docker0 bridge, but firewalld already has that interface assigned to the public zone.

[fleamour]

OK. Makes sense. Thank you for explanation. How do I resolve the bad thing? Did I misconfigure on setup?

[deano_ferrari]

Report back with the results from

sudo firewall-cmd --get-active-zones
sudo firewall-cmd --get-zone-of-interface=docker0
sudo firewall-cmd --zone=docker --list-all

[fleamour]

@deano_ferrari

sudo firewall-cmd --zone=docker --list-all

fleamour@G41M-COMBO ~> sudo firewall-cmd --get-active-zones
[sudo] password for root: 
docker
  interfaces: br-695c7f020c63
public (default)
  interfaces: docker0 wlp4s1f2u1
fleamour@G41M-COMBO ~> sudo firewall-cmd --get-zone-of-interface=docker0
public
fleamour@G41M-COMBO ~> sudo firewall-cmd --zone=docker --list-all
docker (active)
  target: ACCEPT
  ingress-priority: 0
  egress-priority: 0
  icmp-block-inversion: no
  interfaces: br-695c7f020c63
  sources: 
  services: 
  ports: 
  protocols: 
  forward: no
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 

[deano_ferrari]

Docker is failing because docker0 is assigned to the public firewalld zone, while it looks like docker expects its bridge interfaces to be in the docker zone.

Try moving docker0 to the docker zone, and then restart docker…

sudo firewall-cmd --permanent --zone=public --remove-interface=docker0
sudo firewall-cmd --permanent --zone=docker --add-interface=docker0
sudo firewall-cmd --reload
sudo systemctl restart docker

[fleamour]

I have to thank you profusely!!! Had to reboot, but worked perfectly. I am a copy & paste merchant & maybe coulda read firewalld documentation? But could not do without your help, so thx!!!

[deano_ferrari]

Glad to to have been of help!