bump to v2.0.8 This fixes conmon: option parsing failed: Unknown option --persist-dir.
This update has been submitted for testing by jnovy.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Unable to start podman containers following this update, for example:
podman start heimdall Error: unable to start container "heimdall": container create failed (no logs from conmon): EOF
Deleting and recreating the podman container works fine.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
I should add that this only causes issues after a workstation reboot (ie have a container running then reboot the workstation and attempt to start the container again). Very similar to upstream #4522 https://github.com/containers/libpod/issues/4522
podman start <container> Error: unable to start container "<container>": container create failed (no logs from conmon): EOF
Downgrading conmon solves the problem.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by rhcontainerbot.
I can reproduce as well. I have some pre-upgrade containers. The first podman-start works, the second fails. Same EOF error as mentioned above.
podman-start
This update has been obsoleted.
Please log in to add feedback.
Confirm request to re-trigger tests.
This update has been submitted for testing by jnovy.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Unable to start podman containers following this update, for example:
podman start heimdall Error: unable to start container "heimdall": container create failed (no logs from conmon): EOF
Deleting and recreating the podman container works fine.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
I should add that this only causes issues after a workstation reboot (ie have a container running then reboot the workstation and attempt to start the container again). Very similar to upstream #4522 https://github.com/containers/libpod/issues/4522
podman start <container> Error: unable to start container "<container>": container create failed (no logs from conmon): EOF
Downgrading conmon solves the problem.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by rhcontainerbot.
I can reproduce as well. I have some pre-upgrade containers. The first
podman-startworks, the second fails. Same EOF error as mentioned above.This update has been obsoleted.