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
# touch /tmp/mycid
# podman run --cidfile /tmp/mycid fedora date
Thu Mar 22 15:05:26 UTC 2018
docker fails with a helpful diagnostic:
/usr/bin/docker-current: Container ID file found, make sure the other container isn't running or delete /tmp/mycid.
This is a judgment call: one can imagine a UNIX old-timer ranting about overprotective tools and let me shoot myself in the foot if I want to and get off my lawn. I lean that way myself at times. Still... the cost of debugging a problem is much higher if the cidfile is silently overwritten. I would recommend following the docker convention. (Bonus: I think the diagnostic would be more readable as 'Will not overwrite existing cidfile "/tmp/mycid"')
The text was updated successfully, but these errors were encountered:
Both podman run and create have an option to write the container ID to a file. The option
is called cidfile. If the cidfile exists, we should not create or run a container but rather
output a sensical error message.
Resolves: containers#530
Signed-off-by: baude <[email protected]>
podman happily clobbers an existing cidfile:
docker fails with a helpful diagnostic:
This is a judgment call: one can imagine a UNIX old-timer ranting about overprotective tools and let me shoot myself in the foot if I want to and get off my lawn. I lean that way myself at times. Still... the cost of debugging a problem is much higher if the cidfile is silently overwritten. I would recommend following the docker convention. (Bonus: I think the diagnostic would be more readable as 'Will not overwrite existing cidfile "/tmp/mycid"')
The text was updated successfully, but these errors were encountered: