-
Notifications
You must be signed in to change notification settings - Fork 638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panic: provided file is not a console #3297
Comments
Here is a simple repro:
|
Here is a repro for the compose one as seen on usernetes: compose.yaml
|
FWIW, docker exec gives:
While docker compose exec will just run with it:
@AkihiroSuda @fahedouch do you have an idea on how we should handle this? My naive reading is that this is two fold:
and mmm...
|
Closing this. |
It also happens when run -t in systemd unit. Here is my systemd service unit /usr/local/bin/docker is a symbolic link to /usr/local/bin/nerdctl [Unit] [Service] [Install] I tried privileged mode it is all the same. BTW, podman works just fine in the same setup Here is the result in journalctl The unit tmp-containerd\x2dmount3662397617.mount has successfully entered the 'dead' state. |
Description
Likely while mistakenly starting a container with
-ti
on the CI.We probably want to do better than a panic.
Steps to reproduce the issue
na
Describe the results you received and expected
na
What version of nerdctl are you using?
main
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
No response
The text was updated successfully, but these errors were encountered: