My MicroOS server [1] has docker.service which can be started manually without issues. The service is enabled and loaded. But it does not start at boot which is the problem I’d like to fix.
At the same time I see a containerd.service being loaded and active. This service is disabled (by me) but still autostarts. I do not know what starts this. According to a very relevant thread [2] containerd.service and docker.service might conflict and systemd might decide to launch one and ignore the other. This may be true, but I don’t know how to verify.
This issue started happening around the upgrade from Tumbleweed Transactional Server to MicroOS. Which may be a hint. However I really struggle to debug this issue. I don’t know how to determine what starts containerd.service or why docker.service was disgarded. All I see is that when I start docker.service the containerd.service stops.
Any help is very much appreciated!
Cheers!
.san
Some potentially relevant information.
[1] This system was upgraded from Tumbleweed Transactional Server to MicroOS using similar steps as this post. I’m not sure if this is the correct / official / supported route, but I never found any official documentation around this (other than a Bugzilla ticket that describes removing the role).
[2] I found a very relevant thread but I’ve not been able to make this persist after reboot.