-
Notifications
You must be signed in to change notification settings - Fork 2.6k
--cidfile
support for podman exec
#21256
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
Comments
Thanks for reaching out, @findesgh ! This looks like a nice improvement. Are you interested in opening a PR? |
@vrothberg: I know virtually zero Go 😅. A cursory look at the code suggests that this shouldn't be too hard, however, so might be a good opportunity to learn something. |
Awesome, thanks! Feel free to ask questions here :) You can take a look at the how the other commands implement |
A friendly reminder that this issue had no activity for 30 days. |
Fixes: containers#21256 Signed-off-by: Martin Glatzle <[email protected]>
Fixes: containers#21256 Signed-off-by: Martin Glatzle <[email protected]>
Fixes: containers#21256 Signed-off-by: Martin Glatzle <[email protected]>
@vrothberg I've finally opened a PR in case you'd like to check it out. Sorry for taking ages to get around to doing this! |
Fixes: containers#21256 Signed-off-by: Martin Glatzle <[email protected]>
Fixes: containers#21256 Signed-off-by: Martin Glatzle <[email protected]>
…-support Feature/#21256 extend cidfile support
Feature request description
I've had some situations, where being able to use the
--cidfile
option withpodman exec
would've been convenient. As far as I can tell, however, that is not possible, which strikes me as somewhat odd, since, e.g.stop
,kill
,rm
andpause
/unpause
all support it (I just checked andattach
apparently also does not support it).Suggest potential solution
No response
Have you considered any alternatives?
Workarounds for this exist and are quite straight-forward. One can name a container or use external tools to extract an ID from a cid-file, i.e. this is certainly not a high priority issue.
Additional context
From a UX point of view one might argue that all options to identify a container to a command should be supported by all commands that take a container as argument so one might extend this issue to include
attach
(and possibly others I've overlooked?).The text was updated successfully, but these errors were encountered: