mirror of
https://github.com/projectatomic/atomic.git
synced 2026-02-05 18:45:01 +01:00
2dfeae1356
There were two primary cases where a secondary atomic run with a command would trigger an exception. The first was reported in https://github.com/projectatomic/atomic/issues/1006. Basically it can be summarized as: ``` atomic run registry.fedoraproject.org/fedora:25 date # works fine atomic run registry.fedoraproject.org/fedora:26 date # tries to run in the existing f25 container ``` The second case is as simple as: ``` atomic run registry.fedoraproject.org/fedora:25 date # works fine atomic run registry.fedoraproject.org/fedora:25 date # fails ``` This fails because atomic starts the stopped f25 container and then attempts a docker exec. The exec fails because the 'date' command is short-lived and the container exits prior to the exec being run. We now catch those exceptions and notify the user. We added a `--replace` option to run where atomic will now delete the container in question and re-run it from the correct image. Closes: #1019 Approved by: baude