Apps not auto starting again since updating to v1.4.3

Operating System ZimaOS
1

I have the same issue as the previous v1.4.2 beta in that some container apps do not automatically start. I have to manually start them each time I boot the OS.

I previously posted about the same thing here: More issues with the beta 2 update - #4 by CogZog

2

So, would you please tell us what apps are not loading? Screenshots are helpful.

3

Screenshot_2025-08-15-16-43-18-897_com.android.chrome-edit
Screenshot_2025-08-15-16-43-18-897_com.android.chrome-edit1211×2324 97.7 KB

Screenshot_2025-08-15-16-43-00-980_com.android.chrome-edit
Screenshot_2025-08-15-16-43-00-980_com.android.chrome-edit1220×2305 107 KB

Screenshot_2025-08-15-16-42-40-473_com.android.chrome-edit
Screenshot_2025-08-15-16-42-40-473_com.android.chrome-edit1170×2313 103 KB

Screenshot_2025-08-15-16-42-03-482_com.android.chrome-edit
Screenshot_2025-08-15-16-42-03-482_com.android.chrome-edit1173×2327 104 KB

4

We will investigate your list. And please tell us this:

Will these greyed apps survive in next reboot/restart if you manually start it? Or they won’t start even though you start before the reboot/restart? We need exact list of the survived and not survived apps after your manual start of them. Thanks for your reply.

5

Hi.

All of the greyed out apps can be started manually but all will revert to greyed out on restart.

6

To better help you, I have pmed you.

7

Problem

After updating ZimaOS from version 1.4.2 to 1.4.3, all Docker-based apps stopped working. The Docker service failed to start because it was trying to load an incompatible NVIDIA GPU runtime (nvidia-container-runtime).

Solution

The problem was solved by renaming the Docker service override file that forced the system to use the NVIDIA runtime.

Command:

Bash
mv /etc/systemd/system/docker.service.d/override.conf /etc/systemd/system/docker.service.d/override.conf.disabled

After renaming the file and rebooting, the Docker daemon was able to start normally without attempting to load the GPU runtime. As a result, Docker functionality was restored, but without NVIDIA GPU support.

3 Likes
8

cant move

─── Welcome to Zima OS, root ───
Date: Monday, November 17, 2025 | Uptime: up 27 minutes

root@192:/root ➜ # cat /etc/systemd/system/docker.service.d/override.conf.disabled
cat: /etc/systemd/system/docker.service.d/override.conf.disabled: No such file or directory
root@192:/root ➜ # cat /etc/systemd/system/docker.service.d/override.conf
[Service]
ExecStart=
ExecStart=/usr/bin/dockerd --host=fd:// --add-runtime=nvidia=/usr/bin/nvidia-container-runtime
MountFlags=sharedroot@192:/root ➜ # mv /etc/systemd/system/docker.service.d/override.conf /etc/systemd/system/docker.service.d/override.conf.disabled
mv: cannot overwrite ‘/etc/systemd/system/docker.service.d/override.conf.disabled’: No space left on device
root@192:/root ➜ #