nginx: [emerg] invalid IPv6 address in resolver "[NOTE:]" in /etc/nginx/conf.d/upstreams.conf:2 #171
Comments
dekobon
added a commit
to dekobon/nginx-s3-gateway
that referenced
this issue
Sep 13, 2023
|
Thank you for reporting this! |
|
We probably should be using https://github.com/nginxinc/docker-nginx/blob/master/entrypoint/15-local-resolvers.envsh instead |
4141done
added a commit
that referenced
this issue
Oct 2, 2023
elJosho
pushed a commit
to elJosho/nginx-s3-gateway
that referenced
this issue
Oct 25, 2023
…ginxinc#176) # What Fixes an issue where comments in the `/etc/resolv.conf` would get into the dns resolvers list and cause an error when starting the s3 gateway. ## How Following a suggestion on the issue, the logic from [this file](https://github.com/nginxinc/docker-nginx/blob/master/entrypoint/15-local-resolvers.envsh) in the official NGINX docker container was ported over to replace the existing logic. Given a `/etc/resolv.conf` that looks like this: ``` nameserver 127.0.0.11 nameserver 8.8.4.4 nameserver 94.198.184.14 nameserver 94.198.184.34 # NOTE: the libc resolver may not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver 8.8.8.8 options ndots:0 ``` The existing code would produce this: ``` 127.0.0.11 8.8.4.4 94.198.184.14 94.198.184.34 [NOTE:] The 8.8.8.8 ``` With this change applied it looks like this: ``` 127.0.0.11 8.8.4.4 94.198.184.14 94.198.184.34 8.8.8.8 ``` The startup printout looks like this with the change applied: ``` Origin: http://bucket-1.minio:9000 Region: us-east-1 Addressing Style: virtual AWS Signatures Version: v2 DNS Resolvers: 127.0.0.11 8.8.4.4 94.198.184.14 94.198.184.34 8.8.8.8 Directory Listing Enabled: false Directory Listing Path Prefix: Provide Index Pages Enabled: Append slash for directory enabled: Stripping the following headers from responses: x-amz-; CORS Enabled: 0 /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 ``` ## Notes Ideally we should be incorporating the entrypoint scripts from the official nginx docker image. For now we're just porting key logic to get the issue solved quickly. The integration of these scripts will have some other concerns. An issue has been filed for this work: nginxinc#175
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Poorly constrained
grepin the bash scripts seems to pick up a comment from the/etc/resolv.conffile.To Reproduce
Steps to reproduce the behavior:
docker run --env-file ./settings --publish 8011:80 --name nginx-s3-gateway nginx-s3-gateway:ossExpected behavior
The server starts as expected.
Your environment
Additional context
See this line beginning with
# NOTEand ending innameservers...... it qualifies for the
grepcommands found here: https://github.com/search?q=repo%3Anginxinc%2Fnginx-s3-gateway%20%22grep%20nameserver%22&type=codeSensitive Information
The text was updated successfully, but these errors were encountered: