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.

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

Podman not recognized as container runtime #1501

Closed
severinstrobl opened this issue Nov 21, 2020 · 0 comments · Fixed by #1502
Closed

Podman not recognized as container runtime #1501

severinstrobl opened this issue Nov 21, 2020 · 0 comments · Fixed by #1502

Comments

@severinstrobl
Copy link
Contributor

Actual behavior
When executing kaniko using podman, the container runtime is not detected resulting in kaniko exiting with a warning about not running in a containerized environment and referencing the --force command line flag.

Expected behavior
Kaniko should detect podman as a valid container runtime and run inside of a container without providing the --force flag.

To Reproduce
Steps to reproduce the behavior:

  1. Execute /kaniko/executor inside a podman container for an arbitrary context and Dockerfile.

Triage Notes for the Maintainers

Description Yes/No
Please check if this a new feature you are proposing
Please check if the build works in docker but not in kaniko
Please check if this error is seen when you use --cache flag
Please check if your dockerfile is a multistage dockerfile
severinstrobl added a commit to severinstrobl/kaniko that referenced this issue Nov 21, 2020
@severinstrobl
Switch to runtime detection via bpfd/proc
5424798 
The upstream of github.com/genuinetools/amicontained switched to the
container runtime detection via github.com/genuinetools/bpfd/proc,
which supports a larger range of container runtimes. With this change
(among others) Podman can be detected correctly.

Fixes GoogleContainerTools#1501.
severinstrobl added a commit to severinstrobl/kaniko that referenced this issue Nov 21, 2020
@severinstrobl
Switch to runtime detection via bpfd/proc
1863699 
The upstream of github.com/genuinetools/amicontained switched to the
container runtime detection via github.com/genuinetools/bpfd/proc,
which supports a larger range of container runtimes. With this change
(among others) Podman can be detected correctly.

Fixes GoogleContainerTools#1501.
severinstrobl added a commit to severinstrobl/kaniko that referenced this issue Nov 22, 2020
@severinstrobl
Switch to runtime detection via bpfd/proc
0a75a16 
The upstream of github.com/genuinetools/amicontained switched to the
container runtime detection via github.com/genuinetools/bpfd/proc,
which supports a larger range of container runtimes. With this change
(among others) Podman can be detected correctly.

Fixes GoogleContainerTools#1501.
@severinstrobl severinstrobl mentioned this issue Nov 22, 2020
Merged
4 tasks
tejal29 pushed a commit that referenced this issue Dec 9, 2020
@severinstrobl
Switch to runtime detection via bpfd/proc (#1502)
c2a919a 
The upstream of github.com/genuinetools/amicontained switched to the
container runtime detection via github.com/genuinetools/bpfd/proc,
which supports a larger range of container runtimes. With this change
(among others) Podman can be detected correctly.

Fixes #1501.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switch to runtime detection via bpfd/proc severinstrobl/kaniko
1 participant
@severinstrobl