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
podman.sock seems to be converting default network names to bridge to mimic docker behavior. Even when podman network ls shows the default network name as podman, a RESTful API request to /networks/ still returns the network name as bridge.
This behavior is not consistent with /containers/create. When the network name "bridge" is used in "NetworkingConfig.EndpointsConfig", podman returns 500 saying that "container create: unable to find network with name or ID bridge: network not found"
Steps to reproduce the issue
Steps to reproduce the issue
Run the following script after enabling podman.sock:
Issue Description
podman.sock seems to be converting default network names to
bridge
to mimic docker behavior. Even whenpodman network ls
shows the default network name aspodman
, a RESTful API request to/networks/
still returns the network name asbridge
.This behavior is not consistent with
/containers/create
. When the network name "bridge" is used in "NetworkingConfig.EndpointsConfig", podman returns 500 saying that "container create: unable to find network with name or ID bridge: network not found"Steps to reproduce the issue
Steps to reproduce the issue
Run the following script after enabling podman.sock:
Describe the results you received
Error:
{"cause":"network not found","message":"container create: unable to find network with name or ID bridge: network not found","response":500}
Describe the results you expected
No errors.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
It would be better if there's a switch to turn off all these compat features in podman.sock like converting network names.
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: