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
The podman socket will return a note about the correct content-type that
should be used for a given type of message if it is incorrect.
This is a workaround to automatically correct the content-type and
resubmit the call.
A full correction would be to update all of the different connection
entries but this appears to work correctly in the short term.
Updated the spec tests to use debian:stable instead of wheezy since
wheezy is no longer widely supported
Added podman-specific skips to spec tests for running on podman systems.
Added GitHub Actions since Travis is flaky
Explicitly use URI.open in image pulls to work around potential issues.
Fixes#568
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,8 @@ Usage
34
34
35
35
docker-api is designed to be very lightweight. Almost no state is cached (aside from id's which are immutable) to ensure that each method call's information is up to date. As such, just about every external method represents an API call.
36
36
37
+
At this time, basic `podman` support has been added via the podman docker-compatible API socket.
38
+
37
39
## Starting up
38
40
39
41
Follow the [installation instructions](https://docs.docker.com/install/), and then run:
0 commit comments