https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
The socket is in a non-default location: 
/run/k3s/containerd/containerd.sock
So try 
-v /run/k3s/containerd/containerd.sock:/run/containerd/containerd.sock
m
Yeah, I tried that, but then I start to get file not found issues.
Seems like it is more complicated than docker: https://github.com/containerd/nerdctl/issues/272
f
Yeah, you cannot run 
nerdctl
from inside a container; it needs filesystem access to the image store as well
You could use 
crictl
instead, if that has the functionality you need
m
I'm trying to use it for a build system, to have job isolation.
I'm not familiar with 
crictl
f
Maybe using moby and the docker cli will be simpler?
m
Yeah, probably. I use 
nerdctl
for everything else in my development and pipelines, so was trying to avoid multiple tools.
f
I think 
nerdctl build
will still run the build itself in containers (via buildkitd), so I'm not sure why you would need to run 
nerdctl
itself in a container
m
I'm trying to run a build agent inside a container, and have it spawn additional containers for job / tooling isolation.
I may just run the agent on the host and then spawn the containers from there. Would be much simpler.
👍 1
Thanks @fast-garage-66093!
f
You are welcome!
768 Views
Open in Slack
PreviousNext
Powered by