Podman API returns 500 in case network is not found instead of 404 #7184
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Running
docker-compose build <service-name>
doesn't create the network properly. This happens becausedocker-compose build
(or any otherdocker-compose
command that creates an image) will start by creating a network. It will runGET /v1.24/networks/test_default
and will get a 500 response. However, Docker returns 404 in this case (which makes sense as the network is not found).Steps to reproduce the issue:
Start podman service with
podman system service -t 0 tcp:0.0.0.0:8080
Run
curl
command to get a non-existing network:Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
export DOCKER_HOST=localhost:8080
so that docker-compose will talk with the Podman API service.The text was updated successfully, but these errors were encountered: