Skip to content

Conversation

@debarshiray
Copy link
Member

Podman commit 4a02713c57d874c4 [1] broke 'podman exec' for existing
containers.

Note that support for ConmonPidFile in 'podman inspect' was added in
the same version of Podman as the one that has the breakage caused by
commit 4a02713c57d874c4 [1]. Therefore, there's no need to bump the
minimum required version of Podman. Interim Git snapshots between the
two will only cause the extra hint in the error message to be hidden.

[1] containers/podman@4a02713c57d874c4

containers/podman#2673

Podman commit 4a02713c57d874c4 [1] broke 'podman exec' for existing
containers.

Note that support for ConmonPidFile in 'podman inspect' was added in
the same version of Podman as the one that has the breakage caused by
commit 4a02713c57d874c4 [1]. Therefore, there's no need to bump the
minimum required version of Podman. Interim Git snapshots between the
two will only cause the extra hint in the error message to be hidden.

[1] containers/podman@4a02713c57d874c4

containers/podman#2673
@owtaylor
Copy link
Contributor

The inability to continue using an existing container seems like it would be a severe Podman regression, and I don't think adding a bunch of code to give the user a "throw away your work" message makes sense. I'd suggest that we just work with the Podman maintainers to encourage them to fix this ASAP upstream and in Fedora.

@debarshiray
Copy link
Member Author

The breakage was fixed in Podman itself in containers/podman#2762

@debarshiray debarshiray deleted the wip/rishi/handle-containers-libpod-2673 branch March 28, 2019 19:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants