Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions nginx.conf
Original file line number Diff line number Diff line change
Expand Up @@ -65,13 +65,17 @@ http {
proxy_read_timeout 30s;
proxy_send_timeout 5s;

resolver 127.0.0.11 valid=30s;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is podman DNS daemon 127.0.0.11 as well?
This may also break users who have changed their docker daemon IP address to become something else.

Copy link
Author

@inoa-jboliveira inoa-jboliveira Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not familiar with podman, but I understand 127.11 is not a standard, just something docker chose.

The solution would be to read /etc/resolv.conf and inject resolver into nginx.conf via a template.

There is a similar solution here using a custom entrypoint for nginx
penpot/penpot#5861
https://github.com/penpot/penpot/pull/5967/changes


upstream relay {
server relay:3000;
zone lb_zone_relay 64k;
server relay:3000 resolve;
keepalive 2;
}

upstream sentry {
server web:9000;
zone lb_zone_web 64k;
server web:9000 resolve;
keepalive 2;
}

Expand Down