Repository: nginx/docker-nginx

Issue #601: Nginx stable and latest lost networking after the latest container release
Created: 2021-11-17T13:07:48Z
After the container upgrade in the past few days all our previously working containers suddenly lost network connectivity. This seems to affect both latest and stable, for which the container was upgraded a few days ago. Alpine, for which the image is a bit older is working fine.
Host: Raspbian
Arch: ARM - RPI4
root@juno:~# docker images
REPOSITORY        TAG       IMAGE ID       CREATED        SIZE
nginx             stable    b806e477d1cc   5 hours ago    109MB
nginx             latest    4aa417b5bbfb   5 hours ago    109MB
nginx             alpine    062e12983452   4 days ago     16MB
nginx             1.21.0    a2e43f88ed53   4 months ago   103MB
root@juno:~# docker run -it --rm nginx:latest /bin/bash
root@b950816588c8:/# curl google.com
curl: (28) Resolving timed out after 1094587810065 milliseconds
root@juno:~# docker run -it --rm nginx:stable /bin/bash
root@8efd17fa6cae:/# curl google.com
curl: (28) Resolving timed out after 1091446178065 milliseconds
root@juno:~# docker run -it --rm nginx:1.21.0 /bin/bash
root@2c75bf87a97b:/# curl google.com

<TITLE>301 Moved</TITLE>
301 Moved
The document has moved
here.

Duplicate issue #610: raspberry pi 4 problems with docker and nginx:1.21.4 vs nginx:1.21.3 using as a reverse proxy
Created: 2021-12-10T10:17:59Z
Hi there,
today after "upgrading" my container from nginx:1.21.3 to nginx:1.21.4 I experienced some strange behavior
My browser throws errors like:

504 Gateway Time-out
PR_END_OF_FILE_ERROR

In the nginx-logs there are errors like:
1931/02/16 03:06:35 [error] 24#24: *660 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.100.202, server: gitlab.mydomain.test, request: "GET / HTTP/2.0", upstream: "http://192.168.100.55:8877/", host: "gitlab.mydomain.test"
But if I use nginx:1.21.3 with the same configuration everything is absolutely fine, no errors

I build an own image with Dockerfile and the only difference is "FROM nginx:1.21.3" and "FROM nginx:1.21.4"
And for testing I just change the docker run command like docker run [bind some mounts and ports]  nginx:1.21.3   vs   docker run [bind some mounts and ports]  nginx:1.21.4

Are there any breaking changes, do I make something wrong or what could be the problem? Thank you for your help :)
In general I use a really "basic" configuration like:
#VIRTUALHOSTS

     server {
        #listen 80;
        listen 443;
        listen [::]:443;

        ssl on;
        ssl_certificate /etc/nginx/wildcard_cert.crt;
        ssl_certificate_key /etc/nginx/wildcard_cert.pem;

        server_name www.mydomain.test;

        index index.htm index.html /index.htm;

        location / {
        proxy_pass http://www.mydomain.test:8888/;
        }
}


server {
    #listen 80;
    listen 443;
    #listen [::]:443;

    ssl on;
    ssl_certificate /etc/nginx/wildcard_cert.crt;
    ssl_certificate_key /etc/nginx/wildcard_cert.pem;
    server_name gitlab.mydomain.test;


    index index.htm index.html /index.htm;

    location / {
       proxy_pass http://gitlab.mydomain.test:8877;
       proxy_redirect https://gitlab.mydomain.test:8877 https://gitlab.mydomain.test;
    }

}

Thanks and Best Regards
zenhighzer

Closing comment (2021-12-10T15:28:20Z): hi @zenhighzer !
The change between 1.21.3 and 1.21.4 is move to a newer Debian version, 11.
Overall it looks similar to #601 - can you please check if updating libseccomp and docker fixes the issue for you, similar to #601 (comment) ?
Thanks!