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.

Sign up for GitHub

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

Jump to bottom

Fails to open terminal to an application container with: OCI runtime exec failed #257

Closed

jellyfish-bot opened this issue Jul 7, 2021 · 1 comment

jellyfish-bot commented Jul 7, 2021

[admin] When trying from the hostOS to connect to a container using balena exec -it <container> sh we get:

OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "process_linux.go:93: starting setns process caused "fork/exec /proc/self/exe: no such file or directory"": unknown

This also happens from the webterminal as well.

Seen in a recent OS release, which made it even weirder: balenaOS 2.80.3+rev1 supervisor 12.7.0

The text was updated successfully, but these errors were encountered:

thgreasi commented Jul 7, 2021

Duplicate of #256 b/c JF was slow to open the issue.

thgreasi closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment