All Projects → parabuzzle → craneoperator

parabuzzle / craneoperator

Licence: MIT license
Gives you a simple web interface for browsing around a Docker Registry

Programming Languages

javascript
184084 projects - #8 most used programming language
ruby
36898 projects - #4 most used programming language
HTML
75241 projects
Dockerfile
14818 projects
CSS
56736 projects

Projects that are alternatives of or similar to craneoperator

Registry Cli
Scripts for easy manipulation of docker-registry from command line (and from scripts)
Stars: ✭ 609 (+425%)
Mutual labels:  registry, docker-registry
Dockercheatsheet
🐋 Docker Cheat Sheet 🐋
Stars: ✭ 3,301 (+2745.69%)
Mutual labels:  registry, docker-registry
cleanreg
A small tool to clean up Docker Registries (v2).
Stars: ✭ 48 (-58.62%)
Mutual labels:  registry, docker-registry
Pierone
STUPS' Docker registry with S3 backend, immutable tags and SCM source tracking
Stars: ✭ 57 (-50.86%)
Mutual labels:  registry, docker-registry
Docker registry cli
Docker Registry CLI - Provides search functionality for Docker Registry (UI and CLI)
Stars: ✭ 48 (-58.62%)
Mutual labels:  registry, docker-registry
Docker Registry Ui
The simplest and most complete UI for your private registry
Stars: ✭ 756 (+551.72%)
Mutual labels:  registry, docker-registry
ttl.sh
An anonymous & ephemeral Docker image registry
Stars: ✭ 107 (-7.76%)
Mutual labels:  registry, docker-registry
Search Docker Registry V2 Script.1.0
view-private-registry is a simple bash script for listing images in a private registry v2, docker search registry-v2
Stars: ✭ 34 (-70.69%)
Mutual labels:  registry, docker-registry
Dockerscan
Docker security analysis & hacking tools
Stars: ✭ 1,046 (+801.72%)
Mutual labels:  registry, docker-registry
Login Action
GitHub Action to login against a Docker registry
Stars: ✭ 149 (+28.45%)
Mutual labels:  registry, docker-registry
Datbase
[DEPRECATED] Open data sharing powered by Dat
Stars: ✭ 251 (+116.38%)
Mutual labels:  registry
Alexandrie
An alternative crate registry, implemented in Rust.
Stars: ✭ 251 (+116.38%)
Mutual labels:  registry
docker-ci-deploy
Python script to help push Docker images to a registry using CI services
Stars: ✭ 20 (-82.76%)
Mutual labels:  docker-registry
anthology
A private Terraform registry implementation as an alternative to the official registry.
Stars: ✭ 112 (-3.45%)
Mutual labels:  registry
Registry
The registry of type definitions for TypeScript
Stars: ✭ 235 (+102.59%)
Mutual labels:  registry
Windows11-betterUX
A non-destructive registry preset to improve the default user-experience with windows 10.
Stars: ✭ 21 (-81.9%)
Mutual labels:  registry
Citizen
A Private Terraform Module Registry
Stars: ✭ 230 (+98.28%)
Mutual labels:  registry
Harbor
An open source trusted cloud native registry project that stores, signs, and scans content.
Stars: ✭ 16,320 (+13968.97%)
Mutual labels:  registry
Registry
npm registry documentation
Stars: ✭ 202 (+74.14%)
Mutual labels:  registry
xmutca-rpc
Xmutca-rpc是一个基于netty开发的分布式服务框架,提供稳定高性能的RPC远程服务调用功能,支持注册中心,服务治理,负载均衡等特性,开箱即用。
Stars: ✭ 18 (-84.48%)
Mutual labels:  registry

CraneOperator

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+

VERSION 2.2 Includes a bunch of new requested features!

What's new in Version 2.2?

  • Filtering of container list
  • Filtering of the tag list
  • More layer info
  • Permalinks!
  • Login to the registry through the UI
  • Default tag selection if there's only 1 tag for a container

Circle CI

screenshots/crane_operator.png

Why Crane Operator?

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)

How do I run it?

docker run -d -p 80:80 parabuzzle/craneoperator:latest

How do I configure it?

Available Environment Variables:

note: some variables changed in version 2.2

  • REGISTRY_HOST - the registry host to browse (default: localhost)
  • REGISTRY_PORT - the port of the registry host (default: 5000)
  • REGISTRY_PROTOCOL - the protocol to use (ie: http or https) (default: https)
  • 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)
  • ALLOW_REGISTRY_LOGIN - Adds a login option to the UI for logging into the Registry for each user
  • SESSION_SECRET - The session secret for storing the user credentials passed in via ALLOW_REGISTRY_LOGIN
    • note: You should set this to a long random string if you are using ALLOW_REGISTRY_LOGIN
  • REGISTRY_USERNAME - the username to use if the registry has auth enabled (if ALLOW_REGISTRY_LOGIN enabled, this is overridden by the user's session)
  • REGISTRY_PASSWORD - the password to use if the registry has auth enabled (if ALLOW_REGISTRY_LOGIN enabled, this is overridden by the user's session)
  • TITLE - Changes the brand title (for those that like to change that sort of thing)
  • USERNAME - setting this will activate BASIC AUTH and require this username
  • PASSWORD - optional password for BASIC AUTH (you must set the USERNAME for 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_PROTOCOL=https \
  -e SSL_VERIFY=false \
  -e ALLOW_REGISTRY_LOGIN=true \
  -e REGISTRY_ALLOW_DELETE=true \
  parabuzzle/craneoperator:latest
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].