docker daemon is not running
saggiyogesh opened this issue · comments
Hi,
I've deployed a runner on Kubernetes v1.21 using the manifest file provided in docs.
Have also given privileged
access to this runner pod.
While it is working fine while using the docker run
command to start a runner.
/usr/bin/docker version
Client: Docker Engine - Community
Version: [20](https://github.com/ss/runs/5846992661?check_suite_focus=true#step:5:20).10.14
API version: 1.41
Go version: go1.16.15
Git commit: a[22](https://github.com/ss/runs/5846992661?check_suite_focus=true#step:5:22)4086
Built: Thu Mar [24](https://github.com/ss/runs/5846992661?check_suite_focus=true#step:5:24) 01:48:02 2022
OS/Arch: linux/amd64
Context: default
Experimental: true
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Error: The process '/usr/bin/docker' failed with exit code 1
@saggiyogesh 1.21 uses containerd, no?
Im using 1.22 on k3s:
myoung@cluster21:~$ sudo ls /run/k3s/containerd/containerd.sock
/run/k3s/containerd/containerd.sock
so here I'd use:
volumes:
- hostPath:
path: /run/k3s/containerd/containerd.sock
name: containerdsocket
volumeMounts:
- name: containerdsocket
mountPath: /var/run/containerd/containerd.sock
However it doesnt look like github runners support containerd
Hi,
I'm using managed K8s, where cri-o is the container runtime.
Need to check the sock for the same.
@saggiyogesh just FYI continer in container wont work, they only support docker currently. I made a note in the README
As for this: there's nothing I can do until containerd is supported