You might be right… but I’d suggest we let the engineers come to the same conclusion. I’m not sure why others are not reporting a similar issue.
The trueNAS team may have a preferred method for shutting down and restarting.
1 Like
I’ll test it on a clean install to eliminate any possible errors.
Incus is indeed complementary to Docker at the current stage, but Incus is also constantly adding Docker features. Perhaps in a year or two, TrueNAS will abandon Docker and switch to using Incus to manage all containers and VMs.
TrueNAS has made several drastic technical route adjustments in history, including switching from FreeBSD to Linux, from Docker to K3s (later abandoning K3s and switching back to Docker), from KVM to Incus, etc.
If one day, TrueNAS switches from Incus back to KVM or to other solutions, it will not be surprising.
Truenas never officially started with docker support. Docker was just the runtime for the k3s apps system. k3s then made an upstream change from docker to containerd as runtime. As the docker part of the os was not needed anymore to run the k3s apps, truenas removed it. Naturally the folks who used the inofficial part of docker got bitten in the a** by that.
Given the changes in the past 12 months I am closing this request and recommend if this topic needs attention that a fresh feature request based on what is available in 25.10 is raised.