Skip to content
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

/dev cannot be mounted when podman-run started with -t option. #150

Closed
smekkley opened this issue Oct 29, 2019 · 1 comment · Fixed by #151
Closed

/dev cannot be mounted when podman-run started with -t option. #150

smekkley opened this issue Oct 29, 2019 · 1 comment · Fixed by #151
Assignees

Comments

@smekkley
Copy link

/kind bug

$ podman --version
podman version 1.6.1

The following command fails with rootless podman.

$ podman run --rm -v /dev:/dev -it fedora /bin/bash
Error: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused \"open /dev/console: permission denied\"": OCI runtime permission denied error

The current workaround is to..

$ podman run --rm -v /dev:/dev -i fedora /bin/bash
$ podman exec -it `podman ps -q` /bin/bash
@giuseppe giuseppe self-assigned this Oct 29, 2019
@giuseppe giuseppe transferred this issue from containers/podman Oct 29, 2019
giuseppe added a commit to giuseppe/crun that referenced this issue Oct 29, 2019
ignore errors if the file cannot be created as it might already
exist.  We are anyway going to create a mount on top of it and we'll
catch possible errors during the mount itself.

Closes: containers#150

Signed-off-by: Giuseppe Scrivano <[email protected]>
@giuseppe
Copy link
Member

opened a PR: #151

giuseppe added a commit to giuseppe/crun that referenced this issue Oct 30, 2019
if the file cannot be created, check if it already exists before
raising an error.

Closes: containers#150

Signed-off-by: Giuseppe Scrivano <[email protected]>
dfaggioli added a commit to dfaggioli/microos-toolbox that referenced this issue Mar 23, 2020
As described by this libpod issue:

containers/podman#4900

a rootless privileged container refuses to start if anything
has changed in the host device layout since the container
creation.

Using '-v /dev:/dev:rslave' helps, but then we run into
this other issue (about tty permissions):

containers/crun#150

Fix that too by slightly changing container creation.

Using 'sleep +Inf' comes from Fedora Silverblue
toolbox.

This was described in our issue:
openSUSE#3

Signed-off-by: Dario Faggioli <[email protected]>
dfaggioli added a commit to dfaggioli/microos-toolbox that referenced this issue Mar 23, 2020
As described by this libpod issue:

containers/podman#4900

a rootless privileged container refuses to start if anything
has changed in the host device layout since the container
creation.

Using '-v /dev:/dev:rslave' helps, but then we run into
this other issue (about tty permissions):

containers/crun#150

Fix that too by slightly changing container creation.

Using 'sleep +Inf' comes from Fedora Silverblue
toolbox.

This was described in our issue:
openSUSE#3

Signed-off-by: Dario Faggioli <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants