2023-05-01 15:16:01 -04:00
|
|
|
[Git](https://code.nephatrine.net/NephNET/docker-registry/src/branch/master) |
|
2020-01-02 18:29:18 -05:00
|
|
|
[Docker](https://hub.docker.com/r/nephatrine/docker-registry/) |
|
2023-05-01 16:53:53 -04:00
|
|
|
[unRAID](https://code.nephatrine.net/NephNET/unraid-containers)
|
2020-01-02 18:29:18 -05:00
|
|
|
|
|
|
|
|
# Docker Registry
|
|
|
|
|
|
|
|
|
|
This docker image contains a Docker Registry server to self-host your own
|
|
|
|
|
docker registry.
|
|
|
|
|
|
2023-05-01 15:16:01 -04:00
|
|
|
To secure this service, we suggest a separate reverse proxy server, such as an
|
|
|
|
|
[NGINX](https://nginx.com/) container.
|
2020-01-02 21:52:04 -05:00
|
|
|
|
2023-05-01 15:16:01 -04:00
|
|
|
- [Alpine Linux](https://alpinelinux.org/) w/ [S6 Overlay](https://github.com/just-containers/s6-overlay)
|
2020-01-02 18:29:18 -05:00
|
|
|
- [Docker Registry](https://docs.docker.com/registry/)
|
|
|
|
|
|
|
|
|
|
You can spin up a quick temporary test container like this:
|
|
|
|
|
|
|
|
|
|
~~~
|
|
|
|
|
docker run --rm -p 5000:5000 -it nephatrine/docker-registry:latest /bin/bash
|
|
|
|
|
~~~
|
|
|
|
|
|
2020-02-08 17:37:02 -05:00
|
|
|
## Docker Tags
|
|
|
|
|
|
2022-03-03 14:07:19 -05:00
|
|
|
- **nephatrine/docker-registry:latest**: Registry Main / Alpine Latest
|
2020-02-08 17:37:02 -05:00
|
|
|
|
2020-01-02 18:29:18 -05:00
|
|
|
## Configuration Variables
|
|
|
|
|
|
|
|
|
|
You can set these parameters using the syntax ``-e "VARNAME=VALUE"`` on your
|
2020-01-02 21:52:04 -05:00
|
|
|
``docker run`` command. Some of these may only be used during initial
|
|
|
|
|
configuration and further changes may need to be made in the generated
|
|
|
|
|
configuration files.
|
2020-01-02 18:29:18 -05:00
|
|
|
|
|
|
|
|
- ``PUID``: Mount Owner UID (*1000*)
|
|
|
|
|
- ``PGID``: Mount Owner GID (*100*)
|
|
|
|
|
- ``TZ``: System Timezone (*America/New_York*)
|
|
|
|
|
|
|
|
|
|
## Persistent Mounts
|
|
|
|
|
|
|
|
|
|
You can provide a persistent mountpoint using the ``-v /host/path:/container/path``
|
|
|
|
|
syntax. These mountpoints are intended to house important configuration files,
|
|
|
|
|
logs, and application state (e.g. databases) so they are not lost on image
|
|
|
|
|
update.
|
|
|
|
|
|
2020-01-02 21:52:04 -05:00
|
|
|
- ``/mnt/config``: Persistent Data.
|
2020-01-02 18:29:18 -05:00
|
|
|
|
|
|
|
|
Do not share ``/mnt/config`` volumes between multiple containers as they may
|
|
|
|
|
interfere with the operation of one another.
|
|
|
|
|
|
|
|
|
|
You can perform some basic configuration of the container using the files and
|
|
|
|
|
directories listed below.
|
|
|
|
|
|
|
|
|
|
- ``/mnt/config/etc/crontabs/<user>``: User Crontabs. [*]
|
|
|
|
|
- ``/mnt/config/etc/registry/config.yml``: Registry Configuration. [*]
|
|
|
|
|
- ``/mnt/config/etc/logrotate.conf``: Logrotate Global Configuration.
|
|
|
|
|
- ``/mnt/config/etc/logrotate.d/``: Logrotate Additional Configuration.
|
|
|
|
|
|
|
|
|
|
**[*] Changes to some configuration files may require service restart to take
|
|
|
|
|
immediate effect.**
|
|
|
|
|
|
|
|
|
|
## Network Services
|
|
|
|
|
|
|
|
|
|
This container runs network services that are intended to be exposed outside
|
|
|
|
|
the container. You can map these to host ports using the ``-p HOST:CONTAINER``
|
|
|
|
|
or ``-p HOST:CONTAINER/PROTOCOL`` syntax.
|
|
|
|
|
|
|
|
|
|
- ``5000/tcp``: Registry Server. This is the server interface.
|
