containerd / containerd/nerdctl

`nerdctl start` cannot start containers in `Created` or `Exited` status (`OCI runtime create failed: cannot allocate tty if runc will detach without setting console socket`)

Open
#492 7 comments 3 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
10.4k
Forks
826
Avg merge
1d 23h
Merged PRs (30d)
44

Description

**Required behavior:** Allow start Created or Exited containers, either with `nerdctl start` or `nerdctl exec -it`.
**Actual behavior:**
you can run a container, for example: `nerdctl run -it nginx:latest --name nginx-container`.
You can stop it: `nerdctl stop nginx-container`.
**Issue:**
You cannot start again the container neither `nerdctl start nginx-container` nor `nerdctl exec -it nginx-container /bin/sh`.
**Error messages:**
`nerdctl start nginx-container`:
`FATA[0000] OCI runtime create failed: cannot allocate tty if runc will detach without setting console socket: unknown`
`nerdctl exec -it nginx-container /bin/sh`:
`FATA[0000] no running task found: task 0a88555b90488894c72918665b9b14bd6ae96e89676d65ca772b9abf34727884 not found: not found`
**Environment:**
- OS: MacOs Big Sur 11.0.1.
- Backend: Rancher Desktop 0.6.0 (nerdctl 0.12.1).

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.