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
I am currently playing with podman compose utilizing the upstream docker-compose as backend. It always recreates the container because the network config is not as it should be. I added some debug prints to the docker-compose code and it cannot match the networks because the NetworkID returned by podman is wrong.
Running something along the lines of podman inspect 4cb3ce78cde3 --format="{{ json .NetworkSettings.Networks }}"|jq returns:
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: