-
Notifications
You must be signed in to change notification settings - Fork 2.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
Parsing of IMAGE in runlabel command changed behavior in 4d4baba #10192
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
openshift-ci-robot
added
the
kind/bug
Categorizes issue or PR as related to a bug.
label
May 3, 2021
So the question is, is that an expected change? Should we use IMAGE like $IMAGE ? |
KKoukiou
added a commit
to KKoukiou/cockpit-container
that referenced
this issue
May 3, 2021
KKoukiou
added a commit
to KKoukiou/cockpit-container
that referenced
this issue
May 3, 2021
It's been |
Yes we should use IMAGE like $IMAGE, since we did this way back in Atomic. |
Should not be effected by this. |
KKoukiou
added a commit
to KKoukiou/cockpit
that referenced
this issue
May 3, 2021
…man page example The label commands where adjusted to contain IMAGE and NAME as env variables. With newer podman, these are apparently just passed into the environment of the docker run call itself, instead of being string-substituted on the command line. See containers/podman#10192
martinpitt
pushed a commit
to cockpit-project/cockpit
that referenced
this issue
May 4, 2021
…man page example The label commands where adjusted to contain IMAGE and NAME as env variables. With newer podman, these are apparently just passed into the environment of the docker run call itself, instead of being string-substituted on the command line. See containers/podman#10192
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
May 5, 2021
Fixes: containers#10192 Signed-off-by: Daniel J Walsh <[email protected]>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 22, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
/kind bug
Description
runlabel behavior changed in podman version 3.1.1.
Steps to reproduce the issue:
Dockerfile:
Commit which changed behavior:
Describe the results you received:
Error: repository name must be lowercase
Describe the results you expected:
No error :)
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:The text was updated successfully, but these errors were encountered: