-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Container inspect endpoint is not Docker-API compatible #24910
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
Note that this only breaks docker-compose since commit docker/compose@c21d4cf which is in v2.31.0, docker-compose 2.30.3 is fine. |
Got a draft PR at #24950 |
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 6, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 6, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 6, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 6, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 6, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
…s#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 7, 2025
Fixes containers#24910 Signed-off-by: Florian Apolloner <[email protected]>
apollo13
added a commit
to apollo13/podman
that referenced
this issue
Jan 14, 2025
Fixes containers#24910 Signed-off-by: Florian Apolloner <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
I am currently playing with
podman compose
utilizing the upstreamdocker-compose
as backend. It always recreates the container because the network config is not as it should be. I added some debug prints to thedocker-compose
code and it cannot match the networks because theNetworkID
returned by podman is wrong.Running something along the lines of
podman inspect 4cb3ce78cde3 --format="{{ json .NetworkSettings.Networks }}"|jq
returns:Here we can see that
NetworkID
is the network name and not the id of the network (podman network inspect tmp_default
):Steps to reproduce the issue
Steps to reproduce the issue
podman run --rm -it --name testing ubuntu:latest sleep infinity
podman inspect testing --format="{{ json .NetworkSettings.Networks.podman }}"|jq
NetworkID
is the network nameDescribe the results you received
I would have expected the actual
NetworkID
to be shownDescribe the results you expected
The network name is shown as ID
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: