This message was deleted.
# generala
adamant-kite-43734
05/31/2023, 8:11 PMThis message was deleted.
c
creamy-pencil-82913
05/31/2023, 8:16 PMBeing aware of the namespace stuff is a good start, but are you sure that the image you’re building has the same name as the image you’re referencing in the pod?
creamy-pencil-82913
05/31/2023, 8:16 PMAre you also sure that you’re talking to the same containerd instance as the k3s kubelet?
e
early-furniture-67233
05/31/2023, 8:29 PMI believe the name in the yaml file for the deployment is the same name as the image I am building.
early-furniture-67233
05/31/2023, 8:31 PMHmm. As part of this setup I had to enable containerd as "systemctl is-enabled containerd.service" was returning false and nerdctl build was complaing. The K3s install however was already working though. Perhaps there is more than once instance of containerd?
c
creamy-pencil-82913
05/31/2023, 8:42 PMoh yeah, you’re running two different instances of containerd then
creamy-pencil-82913
05/31/2023, 8:42 PMyou should shut down and uninstall the system containerd, and point nerdctl at the k3s containerd socket
e
early-furniture-67233
05/31/2023, 8:47 PMok, thanks. I did that and I'm back to "cannot access containerd socket "/run/containerd/containerd.sock"" so then I tried adding --address /run/k3s/containerd/containerd.sock to nerdctl build and well, it gets further but that still fails with errors about unix:///run/containerd/containerd.sock
early-furniture-67233
05/31/2023, 8:48 PMThere must be something else I am missing here.
c
creamy-pencil-82913
05/31/2023, 9:03 PMat what point does it indicate that it’s still looking at the wrong socket address?
creamy-pencil-82913
05/31/2023, 9:04 PMyou might try using
--address unix:///run/k3s/containerd/containerd.sockcreamy-pencil-82913
05/31/2023, 9:04 PMyou could also just symlink /run/containerd/containerd.sock to /run/k3s/containerd/containerd.sock 🤷
e
early-furniture-67233
05/31/2023, 9:44 PMWell, that seems to work. Seems like I should not have to do that once I specify the socket address though. But thanks! This got me unstuck. I'll report to nerdctl.
39 Views