A web UI for easy private/local Docker Registry integration. Allows you to browse, delete and search for images as well as register multiple registries for large installations.
The application boasts the following features:
-
View all images for all registries (one to many)
-
Further info. page for images for inspection of config. etc
-
Pull copy/paste shortcuts
-
Delete images
-
Search for images
-
Containerized via Docker
-
Exposes the webapp's configuration data as a volume for use with data-containers or simple host directory storage
This project is containerized. You can run with docker right now by simply running:
docker run -p 8080:8080 atcol/docker-registry-ui
and browsing to localhost:8080/.
The app' requires registry configuration which can be supplied once the app's running, or through container environment variables:
docker run -p 8080:8080 -e REG1=http://dev:5000/v1/ -e REG2=http://prod/v1/ atcol/docker-registry-ui
which will run the application and automatically register two registries at the hosts dev and prod respectively,
both running API versions v1. You must provide URLs that include the API version.
Note: don't use localhost in registry URLs! The host needs to be visible from inside the container, so -e REG1=http://localhost/... won't work because localhost will resolve to the container's IP. If registry is running on the host, then remember to use its IP: 172.17.42.1.
The webapp's configuration data is stored inside the container in a H2 database under /var/lib/h2/. You can hold this data on the host machine using the -v flag:
docker run -p 8080:8080 -v /some/data/dir:/var/lib/h2 atcol/docker-registry-ui
which survives container restarts.
You could also use the data-container pattern using --volumes-from:
docker run -v /var/lib/h2 --name="registry_web_data" ubuntu
docker run -p 8080:8080 --volumes-from=registry_web_data atcol/docker-registry-ui
Now all data will be kept in the registry_web_data container.