Just as crane operators can see where all the containers that are in the shipyard, CraneOp gives you a simple web interface for browsing around a Docker Registry running version 2.0+
When you run your own internal docker registry, it can be challenging to find out what has been saved there. I wanted to create a simple and lightweight frontend for browsing my registry. Most solutions that exist are built for registry v1 and don't work with the newer registry v2. (to be honest, its hard enough to even get registry v2 working... browsing it shouldn't be)
docker run -d -p 80:80 parabuzzle/craneoperator:latest
Available Environment Variables:
- REGISTRY_HOST - the registry host to browse (default:
localhost) - REGISTRY_PORT - the port of the registry host (default:
5000) - REGISTRY_PROTO - the protocol to use (ie:
httporhttps) (default:https) - REGISTRY_SSL_VERIFY - should the certificate be verified if using SSL (default:
true) - REGISTRY_PUBLIC_URL - optional url to use for displaying in pull command and footer (default:
REGISTRY_HOST:REGISTRY_PORT) - REGISTRY_USERNAME - the username to use if the registry has basic auth enabled
- REGISTRY_PASSWORD - the password to use if the registry has basic auth enabled
- USERNAME - setting this will activate BASIC AUTH and require this username
- PASSWORD - optional password for BASIC AUTH (you must set the
USERNAMEfor this to work) - REGISTRY_ALLOW_DELETE - when set to true will expose the delete action on images (default: false)
- note: you must enable delete actions on your registry.
- note: some caching schemes may also cause deletes to occur but not be apparent in the UI right away
docker run -d \
-p 80:80 \
-e REGISTRY_HOST=registry.yourdomain.com \
-e REGISTRY_PORT=443 \
-e REGISTRY_PROTO=https \
-e REGISTRY_SSL_VERIFY=false \
-e USERNAME=admin \
-e PASSWORD=s3cr3t \
-e REGISTRY_ALLOW_DELETE=true \
parabuzzle/craneoperator:latest
