502 Bad Gateway nginx container

[CodeCompleter532]

Hello. I am working on switching over to podman for my job for containers for local development from Docker. I am currently getting a 502 bad gateway error with my nginx container when visiting localhost for my locally developed app. Many of my coworkers do not have this problem, and we are all using the same image versions.

I've tried pruning, repulling, and rebuilding the images, reinstalling podman desktop, manually setting my DOCKER_HOST environment variable, and esetting for DNS issues(podman machine set --user-mode-networking).

I know the images I am using work, because I was able to still use docker to start and see my app.

[Wardrop]

This probably has to do with the switch to pasta from slirp4netns. I'm learning Podman myself and have run into all kinds of roadblocks due to this change; talk about a steep learning curve.

For existing containers that have upgraded from podman 4.x to 5.0, they keep using slirt4netns by default to try to ease the transition. Because you're installing podman and creating container from afresh, you'll be defaulting to pasta for your networking where as your colleagues are likely still using slirp4netns. It's quite insidious way to implement such a change.

You can set your default networking back to slirp4netns. See this blog post here for all the info: https://blog.podman.io/2024/03/podman-5-0-breaking-changes-in-detail/