docker run -v /absolute/path/to/serve:/static -p 8080:80 rhzs/nginx-static
This command exposes an nginx server on port 8080 which serves the folder /path/to/serve
from the host.
The image can only be used for static file serving but has with less than 4 MB roughly 1/10 the size of the official nginx image. The running container needs ~1 MB RAM.
To serve your static files over HTTPS you must use another reverse proxy. We recommend træfik as a lightweight reverse proxy with docker integration. Do not even try to get HTTPS working with this image only, as it does not contain the nginx ssl module.
This is an example entry for a docker-compose.yaml
version: '3'
services:
example.org:
image: rhzs/nginx-static
container_name: example.org
ports:
- 8080:80
volumes:
- /path/to/serve:/static
To use nginx-static with træfik 2.1 add an entry to your services in a docker-compose.yaml. To set up traefik look at this simple example.
In the following example, replace everything contained in
services:
traefik:
image: traefik:2.1
# Your treafik config.
...
example.org:
image: rhzs/nginx-static
container_name: example.org
expose:
- 80
labels:
- "traefik.enable=true"
- "traefik.http.routers.<router>.rule=Host(`example.org`)"
- "traefik.http.routers.<router>.entrypoints=<entrypoint>"
# If you want to enable SSL, uncomment the following line.
# - "traefik.http.routers.<router>.tls.certresolver=<certresolver>"
volumes:
- /host/path/to/serve:/static
If traefik and the nginx-static are in distinct docker-compose.yml files, please make sure that they are in the same network.
For a traefik 1.7 example look at an old version of the readme
nginx-static is also suitable for multi-stage builds. This is an example Dockerfile for a static nodejs application:
FROM node:alpine
WORKDIR /usr/src/app
COPY . /usr/src/app
RUN npm install && npm run build
FROM rhzs/nginx-static
RUN apk update && apk upgrade
COPY --from=0 /usr/src/app/dist /static