nginx with s6-overlay using this module s6-overlay-nginx-module. I recommended that you build your own image instead of using this custom image. But I will continue to support this custom release for quite some time until it is no longer being used.Nginx with s6-overlay.
| Registry | Image |
|---|---|
| Docker Hub | docker.io/socheatsok78/nginx-s6 |
| GitHub Package Registry | ghcr.io/socheatsok78/nginx-s6 |
Following platforms for this image are available:
$ docker run --rm mplatform/mquery socheatsok78/nginx-s6:latest
Image: socheatsok78/nginx-s6:latest (digest: sha256:e4bff73f127963083cab672d37bdc40b6bbb64234c090289ad2ba0ff72a142fb)
* Manifest List: Yes (Image type: application/vnd.docker.distribution.manifest.list.v2+json)
* Supported platforms:
- linux/amd64
- linux/arm64
- linux/arm/v7
- linux/arm/v6
latest, mainline, alpinestable, stable-alpinev1.21
1.21, 1.21.3, 1.21.4, 1.21.5, 1.21.61.21-alpine, 1.21.3-alpine, 1.21.4-alpine, 1.21.5-alpine, 1.21.6-alpinev1.22
1.22, 1.22.01.22-alpine, 1.22.0-alpinev1.23
1.23, 1.23.0, 1.23.11.23-alpine, 1.23.0-alpine, 1.23.1-alpine$ docker run --name some-nginx -v /some/content:/usr/share/nginx/html:ro -d socheatsok78/nginx-s6
Alternatively, a simple Dockerfile can be used to generate a new image that includes the necessary content (which is a much cleaner solution than the bind mount above):
FROM socheatsok78/nginx-s6
COPY static-html-directory /usr/share/nginx/html
Place this file in the same directory as your directory of content ("static-html-directory"), run docker build -t some-content-nginx ., then start your container:
$ docker run --name some-nginx -d some-content-nginx
The usage guide are the same as the official nginx docker image.
For s6-overlay usage guide see: https://github.com/just-containers/s6-overlay/#readme
Licensed under the MIT.
Content type
Image
Digest
sha256:99846f9e5…
Size
56.6 MB
Last updated
almost 4 years ago
docker pull socheatsok78/nginx-s6