Docker.socket restart needed on every VM sever reboot

General
1

Hello everyone, this is my first time on this community but been using Docker for some time. I ran into in issue since a fresh installed of Docker Compose on a Ubuntu 24.02 Server VM within Proxmox. I do have some active containers, but every time I attempt to view the output using (Docker ps -a) in terminal, it comes up empty. I have to constantly restart “sudo systemctl restart Docker.socket” to view them every time I reboot the server. What strange is, I’m able to access the containers and the service is active prior to restarting the service. It’s just it will not populate when using docker ps. I didn’t have to do this when I was running this on my previous environment. Hope this makes sense :). Any thoughts please.

Thank you for your time

2

Make sure you have only one Docker on the machine and uninstall the snap package or the docker.io package. You can list the installed packages :slight_smile:

dpkg -l | grep docker
snap list docker

Delete the snap package if you have it, and follow the official guide to install the officially supported Docker CE:

3

You are the man! I guess I didn’t realized I chose the Snap version during setup and I also manually installed it. I uninstalled the snap version, rebooted a few times to test, and can see the “docker ps” output without restarting the service. Thanks again for you help!