I am working on beta version 1.6.1
I’ve tried manually restarting, but it’s not working. I don’t know if it’s related to the cache or something else. Please help!
Before changing anything, I would first verify why Docker is failing.
Can you please share the output of these commands:
docker ps -a
docker info
journalctl -u docker --no-pager | tail -n 100
Also, because you are on ZimaOS 1.6.1 beta, please confirm if this started after an update or after installing/removing any app.
I would not clear cache or remove Docker data yet until the error is confirmed.
1 Like
(__ )( )( / ) / \ / \ / )
/ / )( / / / \ ( O )_**
()(__)_)(/_/_/ _/ (___/
─── Welcome to Zima OS, ———– ───
Date: Saturday, June 13, 2026 | Uptime: up 3 hours, 42 minutes
root@Kerberoz:/root ➜ # docker ps -a
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
root@Kerberoz:/root ➜ # docker info
Client:
Version: 27.5.1
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: 0.16.1
Path: /usr/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: 2.32.4
Path: /usr/lib/docker/cli-plugins/docker-compose
Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info
root@Kerberoz:/root ➜
oot@Kerberoz:/root ➜ # journalctl -u docker --no-pager | tail -n 100
Jun 12 07:39:42 Kerberoz systemd[1]: Failed to start Docker Application Container Engine.
– Boot cbdac90eaeb645b897fbcdf27dd330e0 –
Jun 13 07:25:29 Kerberoz systemd[1]: Starting Docker Application Container Engine…
Jun 13 07:25:33 Kerberoz dockerd[1710]: time=“2026-06-13T07:25:33.005802123-07:00” level=info msg=“Starting up”
Jun 13 07:25:33 Kerberoz dockerd[1710]: time=“2026-06-13T07:25:33.007800918-07:00” level=info msg=“OTEL tracing is not configured, using no-op tracer provider”
Jun 13 07:25:40 Kerberoz dockerd[1710]: time=“2026-06-13T07:25:40.567708855-07:00” level=info msg=“[graphdriver] using prior storage driver: overlay2”
Jun 13 07:25:50 Kerberoz dockerd[1710]: time=“2026-06-13T07:25:50.420904489-07:00” level=info msg=“Processing signal ‘terminated’”
Jun 13 07:25:59 Kerberoz dockerd[1710]: time=“2026-06-13T07:25:59.236292726-07:00” level=info msg=“Loading containers: start.”
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sent signal SIGKILL to main process 1710 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1736 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1737 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1742 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1773 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1812 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1813 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1814 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1815 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1816 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1817 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1819 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1820 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1821 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1823 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1824 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1825 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Sending signal SIGKILL to process 1827 (dockerd) on client request.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Main process exited, code=killed, status=9/KILL
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Failed with result ‘signal’.
Jun 13 07:26:00 Kerberoz systemd[1]: Stopped Docker Application Container Engine.
Jun 13 07:26:00 Kerberoz systemd[1]: docker.service: Consumed 1.554s CPU time, 106M memory peak.
Jun 13 07:26:00 Kerberoz systemd[1]: Starting Docker Application Container Engine…
Jun 13 07:26:00 Kerberoz dockerd[1832]: time=“2026-06-13T07:26:00.715617373-07:00” level=info msg=“Starting up”
Jun 13 07:26:00 Kerberoz dockerd[1832]: time=“2026-06-13T07:26:00.718257151-07:00” level=info msg=“OTEL tracing is not configured, using no-op tracer provider”
Jun 13 07:26:05 Kerberoz dockerd[1832]: time=“2026-06-13T07:26:05.040017459-07:00” level=info msg=“[graphdriver] using prior storage driver: overlay2”
Jun 13 07:26:05 Kerberoz dockerd[1832]: time=“2026-06-13T07:26:05.142231823-07:00” level=info msg=“Loading containers: start.”
Jun 13 07:26:09 Kerberoz dockerd[1832]: time=“2026-06-13T07:26:09.775319998-07:00” 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”
Jun 13 07:26:09 Kerberoz dockerd[1832]: time=“2026-06-13T07:26:09.784331722-07:00” level=info msg=“stopping event stream following graceful shutdown” error=“” module=libcontainerd namespace=moby
Jun 13 07:26:09 Kerberoz dockerd[1832]: failed to start daemon: Error initializing network controller: error creating default “bridge” network: cannot create network ef1aae5f326a3bd1859d4def8c511da2ebb087a5a3cfdb26478668ea964c32bf (docker0): conflicts with network f12fd9803ced8d9797bdbda5b062de20fd6683bf0f2ae910ed7061ed78e4038e (docker0): networks have same bridge name
Jun 13 07:26:09 Kerberoz systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 07:26:09 Kerberoz systemd[1]: docker.service: Failed with result ‘exit-code’.
Jun 13 07:26:09 Kerberoz systemd[1]: Failed to start Docker Application Container Engine.
Jun 13 07:26:09 Kerberoz systemd[1]: docker.service: Consumed 1.194s CPU time, 20.2M memory peak.
Jun 13 07:26:11 Kerberoz systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Jun 13 07:26:11 Kerberoz systemd[1]: Starting Docker Application Container Engine…
Jun 13 07:26:11 Kerberoz dockerd[2283]: time=“2026-06-13T07:26:11.922840251-07:00” level=info msg=“Starting up”
Jun 13 07:26:11 Kerberoz dockerd[2283]: time=“2026-06-13T07:26:11.923930581-07:00” level=info msg=“OTEL tracing is not configured, using no-op tracer provider”
Jun 13 07:26:14 Kerberoz dockerd[2283]: time=“2026-06-13T07:26:14.142038657-07:00” level=info msg=“[graphdriver] using prior storage driver: overlay2”
Jun 13 07:26:14 Kerberoz dockerd[2283]: time=“2026-06-13T07:26:14.336416051-07:00” level=info msg=“Loading containers: start.”
Jun 13 07:26:15 Kerberoz dockerd[2283]: time=“2026-06-13T07:26:15.697254563-07:00” 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”
Jun 13 07:26:15 Kerberoz dockerd[2283]: time=“2026-06-13T07:26:15.701034078-07:00” level=info msg=“stopping event stream following graceful shutdown” error=“” module=libcontainerd namespace=moby
Jun 13 07:26:15 Kerberoz dockerd[2283]: failed to start daemon: Error initializing network controller: error creating default “bridge” network: cannot create network 7862817bd8afd711c4146c6614bd4ffec5d0b8eabf8c89ba65d69e93cd362132 (docker0): conflicts with network f12fd9803ced8d9797bdbda5b062de20fd6683bf0f2ae910ed7061ed78e4038e (docker0): networks have same bridge name
Jun 13 07:26:15 Kerberoz systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 07:26:15 Kerberoz systemd[1]: docker.service: Failed with result ‘exit-code’.
Jun 13 07:26:15 Kerberoz systemd[1]: Failed to start Docker Application Container Engine.
Jun 13 07:26:17 Kerberoz systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Jun 13 07:26:17 Kerberoz systemd[1]: docker.service: Start request repeated too quickly.
Jun 13 07:26:17 Kerberoz systemd[1]: docker.service: Failed with result ‘exit-code’.
Jun 13 07:26:17 Kerberoz systemd[1]: Failed to start Docker Application Container Engine.
Jun 13 07:26:19 Kerberoz systemd[1]: docker.service: Start request repeated too quickly.
Jun 13 07:26:19 Kerberoz systemd[1]: docker.service: Failed with result ‘exit-code’.
Jun 13 07:26:19 Kerberoz systemd[1]: Failed to start Docker Application Container Engine.
Jun 13 11:20:03 Kerberoz systemd[1]: Starting Docker Application Container Engine…
Jun 13 11:20:03 Kerberoz dockerd[222750]: time=“2026-06-13T11:20:03.794838903-07:00” level=info msg=“Starting up”
Jun 13 11:20:03 Kerberoz dockerd[222750]: time=“2026-06-13T11:20:03.797444087-07:00” level=info msg=“OTEL tracing is not configured, using no-op tracer provider”
Jun 13 11:20:04 Kerberoz dockerd[222750]: time=“2026-06-13T11:20:04.598623495-07:00” level=info msg=“[graphdriver] using prior storage driver: overlay2”
Jun 13 11:20:04 Kerberoz dockerd[222750]: time=“2026-06-13T11:20:04.729966590-07:00” level=info msg=“Loading containers: start.”
Jun 13 11:20:06 Kerberoz dockerd[222750]: time=“2026-06-13T11:20:06.899084248-07:00” 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”
Jun 13 11:20:06 Kerberoz dockerd[222750]: time=“2026-06-13T11:20:06.902008202-07:00” level=info msg=“stopping event stream following graceful shutdown” error=“” module=libcontainerd namespace=moby
Jun 13 11:20:06 Kerberoz dockerd[222750]: failed to start daemon: Error initializing network controller: error creating default “bridge” network: cannot create network f3f4bb8f9d8b5a954088e5184acfce7714cb2aa51d59a1bf14bc641dde6513a8 (docker0): conflicts with network f12fd9803ced8d9797bdbda5b062de20fd6683bf0f2ae910ed7061ed78e4038e (docker0): networks have same bridge name
Jun 13 11:20:06 Kerberoz systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 11:20:06 Kerberoz systemd[1]: docker.service: Failed with result ‘exit-code’.
Jun 13 11:20:06 Kerberoz systemd[1]: Failed to start Docker Application Container Engine.
Jun 13 11:20:09 Kerberoz systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Jun 13 11:20:09 Kerberoz systemd[1]: Starting Docker Application Container Engine…
Jun 13 11:20:09 Kerberoz dockerd[223189]: time=“2026-06-13T11:20:09.158141511-07:00” level=info msg=“Starting up”
Jun 13 11:20:09 Kerberoz dockerd[223189]: time=“2026-06-13T11:20:09.160339882-07:00” level=info msg=“OTEL tracing is not configured, using no-op tracer provider”
Jun 13 11:20:11 Kerberoz dockerd[223189]: time=“2026-06-13T11:20:11.750511437-07:00” level=info msg=“[graphdriver] using prior storage driver: overlay2”
Jun 13 11:20:11 Kerberoz dockerd[223189]: time=“2026-06-13T11:20:11.861545862-07:00” level=info msg=“Loading containers: start.”
Jun 13 11:20:14 Kerberoz dockerd[223189]: time=“2026-06-13T11:20:14.659157226-07:00” 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”
Jun 13 11:20:14 Kerberoz dockerd[223189]: time=“2026-06-13T11:20:14.663641290-07:00” level=info msg=“stopping event stream following graceful shutdown” error=“” module=libcontainerd namespace=moby
Jun 13 11:20:14 Kerberoz dockerd[223189]: failed to start daemon: Error initializing network controller: error creating default “bridge” network: cannot create network ac210becbb9ce297dd399c2e86eb3a1b24d91e9afc2f780a2d5d6687ec4ceed2 (docker0): conflicts with network f12fd9803ced8d9797bdbda5b062de20fd6683bf0f2ae910ed7061ed78e4038e (docker0): networks have same bridge name
Jun 13 11:20:14 Kerberoz systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 11:20:14 Kerberoz systemd[1]: docker.service: Failed with result ‘exit-code’.
Jun 13 11:20:14 Kerberoz systemd[1]: Failed to start Docker Application Container Engine.
Jun 13 11:20:16 Kerberoz systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Jun 13 11:20:16 Kerberoz systemd[1]: Starting Docker Application Container Engine…
Jun 13 11:20:16 Kerberoz dockerd[223642]: time=“2026-06-13T11:20:16.916934588-07:00” level=info msg=“Starting up”
Jun 13 11:20:16 Kerberoz dockerd[223642]: time=“2026-06-13T11:20:16.918083451-07:00” level=info msg=“OTEL tracing is not configured, using no-op tracer provider”
Jun 13 11:20:18 Kerberoz dockerd[223642]: time=“2026-06-13T11:20:18.925195240-07:00” level=info msg=“[graphdriver] using prior storage driver: overlay2”
Jun 13 11:20:19 Kerberoz dockerd[223642]: time=“2026-06-13T11:20:19.030801584-07:00” level=info msg=“Loading containers: start.”
Jun 13 11:20:20 Kerberoz dockerd[223642]: time=“2026-06-13T11:20:20.239498212-07:00” 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”
Jun 13 11:20:20 Kerberoz dockerd[223642]: time=“2026-06-13T11:20:20.243790218-07:00” level=info msg=“stopping event stream following graceful shutdown” error=“” module=libcontainerd namespace=moby
Jun 13 11:20:20 Kerberoz dockerd[223642]: failed to start daemon: Error initializing network controller: error creating default “bridge” network: cannot create network d17649d8161ccb5e14326696f99afe04916d5fcde59cd5239f3c9ba786055e01 (docker0): conflicts with network f12fd9803ced8d9797bdbda5b062de20fd6683bf0f2ae910ed7061ed78e4038e (docker0): networks have same bridge name
Jun 13 11:20:20 Kerberoz systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 11:20:20 Kerberoz systemd[1]: docker.service: Failed with result ‘exit-code’.
Jun 13 11:20:20 Kerberoz systemd[1]: Failed to start Docker Application Container Engine.
Jun 13 11:20:22 Kerberoz systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jun 13 11:20:22 Kerberoz systemd[1]: docker.service: Start request repeated too quickly.
Jun 13 11:20:22 Kerberoz systemd[1]: docker.service: Failed with result ‘exit-code’.
Jun 13 11:20:22 Kerberoz systemd[1]: Failed to start Docker Application Container Engine.
root@Kerberoz:/root ➜ #
The problem started after testing several apps from the store, but it wasn’t immediate; the next day nothing worked anymore.
Hi Roman,
The logs show the Docker daemon is not actually crashing during startup.
Docker is failing because it detects a network conflict involving the default bridge interface docker0.
The important error is:
Error initializing network controller:
cannot create network ... (docker0):
conflicts with network ... (docker0):
networks have same bridge name
So at the moment Docker cannot finish starting because it sees multiple network definitions using the same bridge name.
Before making any changes, could you please post the output of:
ip link show docker0
ls -la /var/lib/docker/network/files/
systemctl status docker --no-pager
That should tell us whether this is a stale Docker network database entry, a leftover bridge interface, or something else creating the duplicate docker0 conflict.
I would avoid deleting Docker data or reinstalling Docker until we confirm exactly which network object is causing the conflict.
1 Like
(__ )( )( / ) / \ / \ / )
/ / )( / / / \ ( O )_**
()(__)_)(/_/_/ _/ (___/
─── Welcome to Zima OS, root ───
Date: Saturday, June 13, 2026 | Uptime: up 13 hours, 57 minutes
root@Kerberoz:/root ➜ # ip link show docker0
9: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:4c:61:fb:d5:1b brd ff:ff:ff:ff:ff:ff
root@Kerberoz:/root ➜ # ls -la /var/lib/docker/network/files/
total 276
drwxr-x— 2 root root 4096 Jan 20 23:31 .
drwxr-x— 3 root root 4096 Jan 20 23:31 ..
-rw-r–r-- 1 root root 524288 May 7 07:47 local-kv.db
root@Kerberoz:/root ➜ # systemctl status docker --no-pager
× docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/docker.service.d
└─override.conf
Active: failed (Result: exit-code) since Sat 2026-06-13 11:24:57 MST; 9h ago
Invocation: 95920780504f47d6922ca53a149b235a
TriggeredBy: × docker.socket
Docs: https://docs.docker.com
Main PID: 229072 (code=exited, status=1/FAILURE)
Jun 13 11:24:57 Kerberoz systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jun 13 11:24:57 Kerberoz systemd[1]: docker.service: Start request repeated too quickly.
Jun 13 11:24:57 Kerberoz systemd[1]: docker.service: Failed with result ‘exit-code’.
Jun 13 11:24:57 Kerberoz systemd[1]: Failed to start Docker Application Container Engine.
root@Kerberoz:/root ➜ #
Thanks, that confirms the issue is very likely inside Docker’s saved network database.
Your docker0 bridge exists, and Docker also has its network database here:
/var/lib/docker/network/files/local-kv.db
I would not delete Docker data, containers, images, or volumes.
The safer recovery step is to back up the Docker network database first, then move only that network database out of the way so Docker can recreate the default bridge cleanly.
Please run these commands:
mkdir -p /DATA/AppData/docker-network-backup
cp -a /var/lib/docker/network/files/local-kv.db /DATA/AppData/docker-network-backup/local-kv.db.$(date +%Y%m%d-%H%M%S).bak
ls -lh /DATA/AppData/docker-network-backup/
If the backup is created correctly, then run:
systemctl stop docker docker.socket
mv /var/lib/docker/network/files/local-kv.db /var/lib/docker/network/files/local-kv.db.broken.$(date +%Y%m%d-%H%M%S)
systemctl start docker
Then check:
docker info
docker ps -a
docker network ls
This should not remove your containers or app data. It only resets Docker’s network database, which appears to be where the duplicate docker0 conflict is coming from.
If Docker starts after this, some custom Docker networks may need to be recreated by restarting the relevant apps or compose stacks, but the first priority is getting the Docker daemon running again.
1 Like
Thank you so much for your prompt attention, the problem is solved, you are the best.
1 Like