[Solved] After ZimaOS upgrade v1.4.3 - I am getting cannot connect to Docker daemon errors

snwman · August 23, 2025, 4:20pm

Hi team, I want to report a problem.

I will describe this problem as follows:
Hi ZimaOS Community- I just upgraded to ZimaOS v1.4.3 and I am having major issues. I am running a ZimaBoard 832. Immediately after upgrading I am getting cannot connect to Docker daemon errors. I cannot install any apps from the App Store after this error started. I have hard reset the ZimaBoard a few times with no change.

And I can reproduce the problem like this:

And I remember I did this to my machine before the problem showed up:
Upgraded ZimaOS. Prowler App Update frozen. No Apps will launch. No new Apps can be installed from the App Store

And I have tried these operations to fix it:
Hard Restart of ZimaBoard

And here are the specs of my machine:
ZimeBoard 832
ZimaOS v1.4.3

Zima-Giorgio · August 25, 2025, 7:31am

After the hard reset, did it work properly?

Zima-Giorgio · August 26, 2025, 2:11am

According to the team, this is a known issue with the Docker service. We will release a fix. And before that, you can manually start it by

systemctl restart docker docker.socket

Useful steps for the CLI:

Enter CLI(Settings-> General-> Developer mode view-> SSH Access enable → Web-based terminal)

Log in

Run these commands after logging in:

# Switch to root

sudo -i

systemctl restart docker docker.socket

Look forward to your feedback.

snwman · August 27, 2025, 2:24pm

Hi Giorgio,
Thank you SO MUCH for your response! I had reset the ZimaBoard multiple times and the Docker service did not restart. I can confirm that your guidance on restrating the Docker service as root via CLI completely solved the issue. Thank you again and looking forward the upcoming fix

snwman · August 27, 2025, 3:12pm

Hi Giorgio,
A quick follow up. The CLI Docker reset command does solve the issue. HOWEVER, whenever I restart the ZimaBoard the Docker service is not automatically starting. I can manually restart the Docker service via the CLI and them manually start the individual applications. I hope the upcoming fix will also restart the Docker service when the device is reset. Thanks again for your assistance!

Zima-Giorgio · August 28, 2025, 2:23am

According to some reports, after you restart the machine and launch every app, restarting these apps again may make them start up automatically on the next machine reboot. Look forward to your test and reply.

You can do it like this:

snwman · August 29, 2025, 4:54pm

Hi Giorgio,

Thank you for the guidance. I completed the steps as instructed. Please see the screenshot below:

After the restart you can see that the Apps appear to have started automatically (Jellyfin in this example); however if you look under the expanded System dialogue you will see no apps using either CPU or RAM. If you try to launch the App it is not available, it is the same for all Apps.

If I then go to the CLI and restart Docker

the App’s true state is shown

If I then manually start the App it then functions and you can see it is using CPU and RAM resources

I am happy to test any other scenario if helpful. Please let me know if you need any additional information. Thanks again for the great support!