-
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
Some arguments are case sensitive, others are not #11387
Comments
The boolean options accept both because this how the cli framework handles it. The |
@0b11stan Are there any other flags you've noticed which also have this behavior? They should all be one-line fixes, we just need to know which ones aren't working properly. |
--systemd should definitely get the strings.ToLower() fix. |
Hey, great, that will be an easy fix. No for the moment I do not know of an other option with this behaviour. I tried a few of them but I'm quite new with podman. |
Since boolean flags accept `True` and `False` the systemd flag should do this as well. Fixes containers#11387 Signed-off-by: Paul Holzinger <[email protected]>
/kind bug
Description
There is a case problem in argument's interpretations. Some are case sensitive and others are not, I saw it on the
--systemd
arg (the--tty
arg, for exemple, is not case sensitive) but it may be elsewhere. It's very simple to avoid (obviously just change de case on the command line) and it seems like a very obvious bug but I could not find an existing issue on this topic or the troubleshooting, sorry if it's a double.Steps to reproduce the issue:
This one fails:
When this one is successfull:
Describe the results you received:
Command fails with the following error. Also, the pod is not created.
Describe the results you expected:
I expected the pod to be created.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
The text was updated successfully, but these errors were encountered: