Runpod•3mo ago

Not able to start docker on CPU pods

I used to be able to run docker on CPU pods last year without needing to do anything else than just installing docker, but now I am not able to start docker after installing it.

I get this error:

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

So, naturally I try

sudo systemctl start docker

sudo systemctl start docker

sudo systemctl start docker

sudo systemctl start docker but then I get this error:

System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

Ok, even this doesn't work than I try to run the docker daemon in attached mode by this

sudo dockerd

sudo dockerd

sudo dockerd

sudo dockerdand I get this error at the end and it exits:

INFO[2025-10-18T12:23:16.396620627Z] stopping healthcheck following graceful shutdown  module=libcontainerd
failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to register "bridge" driver: failed to create NAT chain DOCKER: iptables failed: iptables --wait -t nat -N DOCKER: iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Permission denied (you must be root)

 (exit status 4)

INFO[2025-10-18T12:23:16.396620627Z] stopping healthcheck following graceful shutdown  module=libcontainerd
failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to register "bridge" driver: failed to create NAT chain DOCKER: iptables failed: iptables --wait -t nat -N DOCKER: iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Permission denied (you must be root)

 (exit status 4)

INFO[2025-10-18T12:23:16.396620627Z] stopping healthcheck following graceful shutdown  module=libcontainerd
failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to register "bridge" driver: failed to create NAT chain DOCKER: iptables failed: iptables --wait -t nat -N DOCKER: iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Permission denied (you must be root)

 (exit status 4)

INFO[2025-10-18T12:23:16.396620627Z] stopping healthcheck following graceful shutdown  module=libcontainerd
failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to register "bridge" driver: failed to create NAT chain DOCKER: iptables failed: iptables --wait -t nat -N DOCKER: iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Permission denied (you must be root)

 (exit status 4)

How do i make it work?
This is on compute type cpu5g with 2vcpu and 8GB RAM

message.txt10.45KB

riverfog7•10/18/25, 12:31 PM

Docker don't work on runpod

Rriverfog7 Docker don't work on runpod

YoYoOP•10/18/25, 12:46 PM

I know docker doesn't work on their GPU pods. But since when did they stop supporting CPU pods as well?

YoYoOP•10/18/25, 12:46 PM

Just last year I was using their CPU pods and running my compose setups on them just fine

riverfog7•10/18/25, 12:48 PM

https://www.runpod.io/blog/enhanced-cpu-pods-docker-network

Runpod

Enhanced CPU Pods Now Support Docker and Network Volumes | Runpod Blog

We’ve upgraded Runpod CPU pods with Docker runtime and network volume support—giving you more flexibility, better storage options, and smoother dev workflows.

riverfog7•10/18/25, 12:48 PM

@YoYo

riverfog7•10/18/25, 12:49 PM

YoYoOP•10/18/25, 12:51 PM

Wow, that's just super shitty

YoYoOP•10/18/25, 12:51 PM

Anyway thanks for the info @riverfog7

riverfog7•10/18/25, 12:52 PM

lol

riverfog7•10/18/25, 12:52 PM

https://docs.runpod.io/tutorials/pods/build-docker-images

Runpod Documentation

Build Docker Images on Runpod with Bazel - Runpod Documentation

riverfog7•10/18/25, 12:52 PM

try this

riverfog7•10/18/25, 12:52 PM

@YoYo

YoYoOP•10/18/25, 12:56 PM

I had credits left that I loaded last year thought let's just consume them, I can't even do that now.

Rriverfog7 https://docs.runpod.io/tutorials/pods/build-docker-images

YoYoOP•10/18/25, 12:57 PM

Na, I am not doing that. I have to learn a new build tool just to be able to test my container setup. I am going to bother with that.

YYoYo Na, I am not doing that. I have to learn a new build tool just to be able to tes...

Dj•10/18/25, 6:21 PM

We've been experimenting with something called udocker, which might do what you want, but I would recommend retrofitting your existing image just to be the pod itself. Happy to help with that, in general you can just change the start command in the UI.

Not able to start docker on CPU pods

Similar Threads

Similar Threads

Similar Threads