What happened
Using Podman as alternative runtime instead of Docker makes the client container's Nginx instance fail to resolve to the backend. This is, because Nginx is hardcoded to use Docker's DNS IP to resolve the URL, when Podman doesn't use that IP.
Version/commit
No response
Affected browser(s)
No response
Relevant logs/errors
D:\..\..\coop git:(main) ➜ podman compose -f docker-compose.images.yaml logs client
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf differs from the packaged version
/docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2026/07/15 16:07:14 [notice] 1#1: using the "epoll" event method
2026/07/15 16:07:14 [notice] 1#1: nginx/1.27.5
2026/07/15 16:07:14 [notice] 1#1: built by gcc 12.2.0 (Debian 12.2.0-14)
2026/07/15 16:07:14 [notice] 1#1: OS: Linux 6.18.33.1-microsoft-standard-WSL2
2026/07/15 16:07:14 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2026/07/15 16:07:14 [notice] 1#1: start worker processes
2026/07/15 16:07:14 [notice] 1#1: start worker process 23
2026/07/15 16:07:14 [notice] 1#1: start worker process 24
2026/07/15 16:07:14 [notice] 1#1: start worker process 25
2026/07/15 16:07:14 [notice] 1#1: start worker process 26
2026/07/15 16:07:14 [notice] 1#1: start worker process 27
2026/07/15 16:07:14 [notice] 1#1: start worker process 28
2026/07/15 16:07:14 [notice] 1#1: start worker process 29
2026/07/15 16:07:14 [notice] 1#1: start worker process 30
2026/07/15 16:07:14 [notice] 1#1: start worker process 31
2026/07/15 16:07:14 [notice] 1#1: start worker process 32
2026/07/15 16:07:14 [notice] 1#1: start worker process 33
2026/07/15 16:07:14 [notice] 1#1: start worker process 34
10.89.1.6 - - [15/Jul/2026:16:08:57 +0000] "GET / HTTP/1.1" 200 1036 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:153.0) Gecko/20100101 Firefox/153.0" "-"
2026/07/15 16:08:57 [error] 23#23: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2026/07/15 16:08:57 [error] 23#23: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2026/07/15 16:09:02 [error] 23#23: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
10.89.1.6 - - [15/Jul/2026:16:09:02 +0000] "POST / HTTP/1.1" 405 157 "http://localhost:3000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:153.0) Gecko/20100101 Firefox/153.0" "-"
2026/07/15 16:09:07 [error] 23#23: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2026/07/15 16:09:12 [error] 23#23: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
Anything else
While searching around for more information about this, I found this issue: penpot/penpot#5861, which seems to be the same thing happening here.
If relevant, this was tested on Windows with WSL2 as Podman's backend.
Screenshots
No response
Checklist
What happened
Using Podman as alternative runtime instead of Docker makes the client container's Nginx instance fail to resolve to the backend. This is, because Nginx is hardcoded to use Docker's DNS IP to resolve the URL, when Podman doesn't use that IP.
Version/commit
No response
Affected browser(s)
No response
Relevant logs/errors
Anything else
While searching around for more information about this, I found this issue: penpot/penpot#5861, which seems to be the same thing happening here.
If relevant, this was tested on Windows with WSL2 as Podman's backend.
Screenshots
No response
Checklist