-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the ability to run containers #226
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jonathanunderwood The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
e0d7178
to
b7cd8d0
Compare
The Podman REST wait endpoint returns a JSON encoded integer, whereas the Container.wait() function was expecting a JSON object with "Error" and "Status Code" keys (which actually corresponds to the response from the "Podman compat" legacy API). So, we fix that in the Container.wait() method, and in the consuming Container.run() method. See: https://docs.podman.io/en/latest/_static/api.html#tag/containers/operation/ContainerWaitLibpod Signed-off-by: Jonathan G. Underwood <[email protected]>
This is a cosmetic clarification. Signed-off-by: Jonathan G. Underwood <[email protected]>
Signed-off-by: Jonathan G. Underwood <[email protected]>
Signed-off-by: Jonathan G. Underwood <[email protected]>
Signed-off-by: Jonathan G. Underwood <[email protected]>
Signed-off-by: Jonathan G. Underwood <[email protected]>
Signed-off-by: Jonathan G. Underwood <[email protected]>
7fbc9c5
to
6134b4c
Compare
LGTM |
1 similar comment
LGTM |
This set of changes fixes the broken
.run()
capability, and adds some docstrings and clarifications along the way.This fixes #201 and item 3 in #184.