לא מצליח להיכנס לאפליקציה עם ./launcher

תמיכה התקנה

סיכום מבוסס בינה מלאכותית

Users are troubleshooting an error when running ./launcher enter app or docker exec -it app /bin/bash on Ubuntu 22.04, receiving the message: “OCI runtime exec failed: exec failed: unable to start container process: open /dev/pts/1: operation not permitted: unknown”. TechAUmNu reports this on a fresh install with Docker 20.10.17. Falco suggests it may be a bug in runc 1.1.3, referencing a containerd GitHub issue. Benjamin_D confirms the command works on their Ubuntu 22.04.1 system with runc 1.1.3 and containerd 1.6.7. pfaffman notes seeing the same issue on an AWS EC2 instance and advises checking runc and containerd versions via sudo containerd -c and sudo runc -v. EGreg confirms they are the client experiencing the issue and requests tagging if a solution is found. pfaffman clarifies they do not have a solution and had only observed the issue on EGreg’s machine.

1

I am trying to enter the console, but when I use

./launcher enter app

I get this very cryptic error.

Running on ubuntu 22.04, fresh install.

root@discourse:/var/discourse# ./launcher enter app
x86_64 arch detected.
OCI runtime exec failed: exec failed: unable to start container process: open /dev/pts/1: operation not permitted: unknown

Equivalent docker command fails the same way.

root@discourse:/var/discourse# docker exec -it app  /bin/bash --login
OCI runtime exec failed: exec failed: unable to start container process: open /dev/pts/1: operation not permitted: unknown

Docker

root@discourse:/var/discourse# docker --version
Docker version 20.10.17, build 100c701
2

Sounds like a bug on runc 1.1.3 per

https://github.com/containerd/containerd/issues/7219

Can you check your containerd / runc versions?

3

if it helps, on my ubuntu 22.04.1 sandbox, enter app works with

runc version 1.1.3
commit: v1.1.3-0-g6724737
spec: 1.0.2-dev
go: go1.17.13
libseccomp: 2.5.3

containerd containerd.io 1.6.7 0197261a30bf81f1ee8e6a4dd2dea0ef95d67ccb

Docker version 20.10.17, build 100c701

4

I saw this on an AWS EC2 client today. It was a screen share, though, so I can’t get the version information.

It happened both with ./launcher enter app and docker exec -it app bash.

Use these commands to get the version information:

sudo containerd -c
sudo runc -v
5

I’m the client and yes it happened on my machine.
Please tag me if you’ve solved this somehow @TechAUmNu

6

You need to run those commands on the VM where it was broken and report the version information here.

7

Have you been able to solve it?

@pfaffman @TechAUmNu

8

Oh. Sorry. I don’t have an answer. I guess it was your machine where I saw it and I haven’t touched another aws machine.