-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Podman not recognized as container runtime #1501
Comments
severinstrobl
added a commit
to severinstrobl/kaniko
that referenced
this issue
Nov 21, 2020
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
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
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.
4 tasks
tejal29
pushed a commit
that referenced
this issue
Dec 9, 2020
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
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:
/kaniko/executor
inside a podman container for an arbitrary context and Dockerfile.Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: