Replies: 2 comments 3 replies
-
This is a bug report, not a "question" 🙂 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for comments !!! |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Question
If we try to attach to a container that has been started as shown below, the following error will occur.
Is this the expected behavior?
There seems to be an error in the following part of nerdctl, but I'm in trouble because I don't know how to fix it.
nerdctl/pkg/cioutil/container_io_unix.go
Line 122 in 9ce158b
Note that Docker doesn't cause such an error, and we can attach it to a container.
Environments
I'm using the following versions of containerd and nerdctl.
[haytok@lima-finch workspace]$ containerd --version containerd github.com/containerd/containerd v1.7.13 7c3aca7a610df76212171d200ca3811ff6096eb8 [haytok@lima-finch workspace]$ nerdctl version WARN[0000] failed to inspect the rootless containerd socket address error="stat /run/user/504/containerd-rootless: no such file or directory" Client: Version: v1.7.3 OS/Arch: linux/amd64 Git commit: 0a464409d0178e16d3d2bed36222937ec3fc9c77 buildctl: Version: v0.12.5 GitCommit: bac3f2b673f3f9d33e79046008e7a38e856b3dc6
Note that containerd and nerdctl are running in Lima launched from Finch.
Beta Was this translation helpful? Give feedback.
All reactions