Cannot create network with name "bridge" because it conflicts with a valid network mode

[albertdb]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Cannot create a network named bridge to make badly written applications (but not changeable) that depend on Docker default network name work.

Steps to reproduce the issue:

1. podman network create bridge

Describe the results you received:

Error: cannot create network with name "bridge" because it conflicts with a valid network mode

Describe the results you expected:

Network is created.

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

4.1.0

Package info (e.g. output of rpm -q podman or apt list podman):

(42/43) Installing podman (4.1.0-r1)

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes

Additional environment details (AWS, VirtualBox, physical, etc.):

Podman inside Alpine container.

[Luap99]

You should not have to create a network called bridge. Podman already accepts --network bridge and will automatically map this to the default podman network.

[albertdb]

You should not have to create a network called bridge. Podman already accepts --network bridge and will automatically map this to the default podman network.

@Luap99 It doesn't seem to be the case though the API.

Status 404: {"cause":"network not found","message":"unable to find network with name or ID bridge: network not found","response":404}

[Luap99]

Please provide a full reproducer

[albertdb]

Please provide a full reproducer

Using this project as a basis https://github.com/devonfw-sample/devon4quarkus-reference

Run inside a Docker container (in my case a GitLab runner) with image maven:3-eclipse-temurin-11-alpine and mounting the project code, the following commands:

apk add --no-cache podman podman-docker git
echo "export TESTCONTAINERS_RYUK_DISABLED=true" >> ~/.bashrc
source ~/.bashrc
podman system service --time=0 unix:/var/run/docker.sock & sleep 5
podman network ls
docker run --rm hello-world
# you can do a git clone here and cd into the dir, instead of mounting the project code
mvn package

Last command with throw at the end:

Status 404: {"cause":"network not found","message":"unable to find network with name or ID bridge: network not found","response":404}

[Luap99]

I don't have time to run such big complicated reproducers, please provide the exact API call where we error.
You can use podman system service --log-level debug to see the calls

[albertdb]

I don't have time to run such big complicated reproducers, please provide the exact API call where we error. You can use podman system service --log-level debug to see the calls

Oh, that's a very useful flag for this case. Here's the relevant API call:

@ - - [20/Jul/2022:12:29:47 +0000] "GET /v1.30/networks/bridge HTTP/1.1" 404 122 "" "okhttp/3.14.4"

[Luap99]

Should be fixed in the next release (v4.2).

As workaround you could also try setting the default network name to bridge in containers.conf.