1
0
Fork 0
Container w/ Docker Registry
This repository has been archived on 2023-06-13. You can view files and clone it, but cannot push or open issues or pull requests.
Go to file
Daniel Wolf ac3764ecb0
Build Container Image / build_amd64 (push) Successful in 1m25s Details
Build Container Image / build_arm64 (push) Successful in 3m12s Details
Build Container Image / build_armhf (push) Successful in 8m18s Details
Build Container Image / build_manifest (push) Successful in 6s Details
Build Container Image / publish_arm64 (push) Successful in 12s Details
Build Container Image / publish_armhf (push) Successful in 27s Details
Build Container Image / publish_amd64 (push) Successful in 33s Details
Build Container Image / publish_manifest (push) Successful in 10s Details
remove duplicate describe step
2023-05-02 16:29:38 -04:00
.gitea/workflows remove duplicate describe step 2023-05-02 16:29:38 -04:00
override/etc explicitly exit 0 2022-03-03 17:14:21 -05:00
.dockerignore update .dockerignore #noci 2023-05-01 15:19:51 -04:00
.gitignore update .gitignore 2022-03-02 18:58:50 -05:00
Dockerfile use golang-specific builder 2023-04-17 12:02:21 -04:00
LICENSE.md migrate from drone to gitea-runner 2023-05-01 15:16:01 -04:00
README.md update unraid container url #noci 2023-05-01 16:53:53 -04:00

README.md

Git | Docker | unRAID

Docker Registry

This docker image contains a Docker Registry server to self-host your own docker registry.

To secure this service, we suggest a separate reverse proxy server, such as an NGINX container.

You can spin up a quick temporary test container like this:

docker run --rm -p 5000:5000 -it nephatrine/docker-registry:latest /bin/bash

Docker Tags

  • nephatrine/docker-registry:latest: Registry Main / Alpine Latest

Configuration Variables

You can set these parameters using the syntax -e "VARNAME=VALUE" on your 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.

  • 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.

  • /mnt/config: Persistent Data.

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.