podman does not support entrypoint #321
Assignees
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
|
@baude Can you get this fixed before we announce on Monday? |
|
yes working on it now |
baude
added a commit
to baude/podman
that referenced
this issue
Feb 10, 2018
When an image has an ENTRYPOINT defined, we should be honoring it. The problem is described in issue containers#321. Also, added buildah binary to test runtimes for testing entrypoint and will also allow us to test podman build as well. Signed-off-by: baude <bbaude@redhat.com>
baude
added a commit
to baude/podman
that referenced
this issue
Feb 10, 2018
When an image has an ENTRYPOINT defined, we should be honoring it. The problem is described in issue containers#321. Also, added buildah binary to test runtimes for testing entrypoint and will also allow us to test podman build as well. Signed-off-by: baude <bbaude@redhat.com>
rh-atomic-bot
pushed a commit
that referenced
this issue
Feb 11, 2018
When an image has an ENTRYPOINT defined, we should be honoring it. The problem is described in issue #321. Also, added buildah binary to test runtimes for testing entrypoint and will also allow us to test podman build as well. Signed-off-by: baude <bbaude@redhat.com> Closes: #322 Approved by: rhatdan
|
This is verified to be working now. |
baude
pushed a commit
to baude/podman
that referenced
this issue
Aug 31, 2019
bandwidth: get bandwidth interface in host ns through container interface
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to reproduce the issue:
This is just an example
buildah config --entrypoint "ls -al /etc" my-container
buildah inspect my-container // it's set correctly
buildah commit my-container ls
podman run -it ls
Describe the results you received:
You get an error asking you for a command
Describe the results you expected:
The long listing of a directory /etc
Additional information you deem important (e.g. issue happens only occasionally):
The entries in entrypoint are set correctly. Docker has no problem using them in the image.
Output of
podman version:Additional environment details (AWS, VirtualBox, physical, etc.):
Fedroa 27, physical
The text was updated successfully, but these errors were encountered: