You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've had some situations, where being able to use the --cidfile option with podman 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 and pause/unpause all support it (I just checked and attach 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:
@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.
I'll make a stab at it, we'll see how it goes.
Awesome, thanks! Feel free to ask questions here :) You can take a look at the how the other commands implement --cidfile. The commit would also need a test but we can collaborate on that.
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: