sudo systemctl enable docker.service
sudo systemctl enable containerd.service
Reinicia após executar esses comandos.
Você está usando systemd ou sysvinit? Posta a saída desse comando:
ps -p 1 -o comm=
SystemD
$ ps -p 1 -o comm=
systemd
curl -fsSL https://get.docker.com/rootless -o get-docker.sh
sh get-docker.sh
Executa esses comandos e vê o que acontece.
sh get-docker.sh
# Installing stable version 29.1.5
# Executing docker rootless install script, commit: f381ee68b32e515bb4dc034b339266aff1fbc460
Aborting because rootful Docker is running and accessible. Set FORCE_ROOTLESS_INSTALL=1 to ignore.
sudo sh get-docker.sh
# Installing stable version 29.1.5
# Executing docker rootless install script, commit: f381ee68b32e515bb4dc034b339266aff1fbc460
Refusing to install rootless Docker as the root user
Está rodando, mas o WinBoat diz que não. Vou testar aqui na minha distribuição e ver se acontece a mesma coisa.
Thanks. 
Fico no aguardo.
Eu não cheguei a instalar o Docker completamente, mas aqui o WinBoat indica que o daemon está rodando:
Se você fez tudo corretamente de acordo com a wiki do Docker e o problema persiste, talvez seja a distribuição.
Reinicia o sistema e executa esse comando:
sudo dockerd
sudo dockerd
INFO[2026-01-19T17:12:20.580755079-03:00] Starting up
failed to start daemon, ensure docker is not running or delete /var/run/docker.pid: process with PID 1395 is still running
hmmmmm… eita
Isso aconteceu depois de reiniciar o sistema? Tente encerrar esses processos com o kill.
Tive que matar 3 processo 1395, 7841, 8219.
INFO[2026-01-19T17:15:31.806509825-03:00] Starting up
INFO[2026-01-19T17:15:31.807080142-03:00] OTEL tracing is not configured, using no-op tracer provider
INFO[2026-01-19T17:15:31.807149414-03:00] CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory dir=/var/run/cdi
INFO[2026-01-19T17:15:31.807159571-03:00] CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory dir=/etc/cdi
INFO[2026-01-19T17:15:31.814599973-03:00] Creating a containerd client address=/run/containerd/containerd.sock timeout=1m0s
INFO[2026-01-19T17:15:31.821741458-03:00] Loading containers: start.
INFO[2026-01-19T17:15:31.821772482-03:00] Starting daemon with containerd snapshotter integration enabled
INFO[2026-01-19T17:15:31.822818143-03:00] Restoring containers: start.
INFO[2026-01-19T17:15:31.856605319-03:00] Deleting nftables IPv4 rules error="exit status 1"
INFO[2026-01-19T17:15:31.893969070-03:00] Deleting nftables IPv6 rules error="exit status 1"
INFO[2026-01-19T17:15:33.401861574-03:00] Loading containers: done.
INFO[2026-01-19T17:15:33.407440907-03:00] Docker daemon commit=3b01d64 containerd-snapshotter=true storage-driver=overlayfs version=29.1.5
INFO[2026-01-19T17:15:33.407493658-03:00] Initializing buildkit
INFO[2026-01-19T17:15:33.410314033-03:00] Completed buildkit initialization
INFO[2026-01-19T17:15:33.414272506-03:00] Daemon has completed initialization
INFO[2026-01-19T17:15:33.414339261-03:00] API listen on /var/run/docker.sock
Não passa daqui.
Quando eu executei os comandos para iniciar o daemon na inicialização, consegui iniciar o WinBoat. Tenta executar eles novamente e reinicia.
Então acho que, apesar do WinBoat não detectar a inicialização do daemon com o dockerd, o problema pode ser a distribuição. O systemctl deveria ter funcionado.
Vou abrir uma maquina virtual com o MX Linux e testar isso.