linuxserver/nginx. These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
| Parameter | Function |
|---|---|
-p 80:80 | http |
-p 443:443 | https |
-e PUID=1000 | for UserID - see below for explanation |
-e PGID=1000 | for GroupID - see below for explanation |
-e TZ=Etc/UTC | specify a timezone to use, see this list. |
-e NGINX_AUTORELOAD= | Set to true to enable automatic reloading of confs on change without stopping/restarting nginx. Your filesystem must support inotify. This functionality was previously offered via mod. |
-e NGINX_AUTORELOAD_WATCHLIST= | A pipe-separated list of additional folders for auto reload to watch in addition to /config/nginx |
-v /config | Persistent config files |
--read-only=true | Run container with a read-only filesystem. Please read the docs. |
You can set any environment variable from a file by using a special prepend FILE__.
As an example:
bash-e FILE__MYVAR=/run/secrets/mysecretvariable
Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1000 and PGID=1000, to find yours use id your_user as below:
bashid your_user
Example output:
textuid=1000(your_user) gid=1000(your_user) groups=1000(your_user)
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
Shell access whilst the container is running:
bashdocker exec -it nginx /bin/bash
To monitor the logs of the container in realtime:
bashdocker logs -f nginx
Container version number:
bashdocker inspect -f '{{ index .Config.Labels "build_version" }}' nginx
Image version number:
bashdocker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nginx:latest
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
Update images:
All images:
bashdocker-compose pull
Single image:
bashdocker-compose pull nginx
Update containers:
All containers:
bashdocker-compose up -d
Single container:
bashdocker-compose up -d nginx
You can also remove the old dangling images:
bashdocker image prune
Update the image:
bashdocker pull lscr.io/linuxserver/nginx:latest
Stop the running container:
bashdocker stop nginx
Delete the container:
bashdocker rm nginx
Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
You can also remove the old dangling images:
bashdocker image prune
[!TIP] We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
If you want to make local modifications to these images for development purposes or just to customize the logic:
bashgit clone [***] cd docker-nginx docker build \ --no-cache \ --pull \ -t lscr.io/linuxserver/nginx:latest .
The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static
bashdocker run --rm --privileged lscr.io/linuxserver/qemu-static --reset
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.



manifest unknown 错误
TLS 证书验证失败
DNS 解析超时
410 错误:版本过低
402 错误:流量耗尽
身份认证失败错误
429 限流错误
凭证保存错误
来自真实用户的反馈,见证轩辕镜像的优质服务