# Cannot use ./launcher enter app

**URL:** <https://meta.discourse.org/t/cannot-use-launcher-enter-app/236323>\
**Category:** Self-hosting\
**Created:** [August 16, 2022, 3:03pm UTC](https://meta.discourse.org/t/cannot-use-launcher-enter-app/236323 "2022-08-16T15:03:53Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![TechAUmNu](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techaumnu/32/270867_2.png) [@TechAUmNu](https://meta.discourse.org/u/TechAUmNu)\
**Post date:** [August 16, 2022, 3:03pm UTC](https://meta.discourse.org/t/cannot-use-launcher-enter-app/236323/1 "2022-08-16T15:03:53Z")

</div>

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.

```plaintext
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.

```plaintext
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

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

```

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [August 16, 2022, 4:04pm UTC](https://meta.discourse.org/t/cannot-use-launcher-enter-app/236323/2 "2022-08-16T16:04:03Z")

</div>

Sounds like a bug on runc 1.1.3 per

[https://github.com/containerd/containerd/issues/7219](https://github.com/containerd/containerd/issues/7219)

Can you check your containerd / runc versions?

---

<div class="post-metadata">

**Author:** ![Benjamin\_D](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/benjamin_d/32/277831_2.png) [@Benjamin\_D](https://meta.discourse.org/u/Benjamin_D)\
**Post date:** [August 16, 2022, 8:21pm UTC](https://meta.discourse.org/t/cannot-use-launcher-enter-app/236323/3 "2022-08-16T20:21:25Z")

</div>

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

```plaintext
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`

---

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [August 16, 2022, 8:38pm UTC](https://meta.discourse.org/t/cannot-use-launcher-enter-app/236323/4 "2022-08-16T20:38:46Z")

</div>

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:

```plaintext
sudo containerd -c
sudo runc -v

```

---

<div class="post-metadata">

**Author:** ![EGreg](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/egreg/32/133614_2.png) [@EGreg](https://meta.discourse.org/u/EGreg)\
**Post date:** [August 16, 2022, 9:06pm UTC](https://meta.discourse.org/t/cannot-use-launcher-enter-app/236323/5 "2022-08-16T21:06:46Z")

</div>

> [@pfaffman](#):
>
> ```plaintext
> sudo containerd -c
> sudo runc -v
> 
> ```

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

---

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [August 16, 2022, 9:18pm UTC](https://meta.discourse.org/t/cannot-use-launcher-enter-app/236323/6 "2022-08-16T21:18:43Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![EGreg](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/egreg/32/133614_2.png) [@EGreg](https://meta.discourse.org/u/EGreg)\
**Post date:** [September 4, 2022, 9:10pm UTC](https://meta.discourse.org/t/cannot-use-launcher-enter-app/236323/7 "2022-09-04T21:10:16Z")

</div>

Have you been able to solve it?

@pfaffman @TechAUmNu

---

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [September 4, 2022, 10:01pm UTC](https://meta.discourse.org/t/cannot-use-launcher-enter-app/236323/8 "2022-09-04T22:01:41Z")

</div>

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.