Insecure Registry¶
Use an insecure registry for local development only.
Warning
Insecure registries do not encrypt traffic or verify server identity. Do not use this pattern for production deployments.
Create the Compose File¶
Create docker-compose-registry-insecure.yml:
version: '3.8'
services:
registry-ui:
image: joxit/docker-registry-ui:main
restart: always
ports:
- 80:80
environment:
- SINGLE_REGISTRY=true
- REGISTRY_TITLE=Docker Registry UI
- DELETE_IMAGES=true
- SHOW_CONTENT_DIGEST=true
- NGINX_PROXY_PASS_URL=http://registry:5000
- SHOW_CATALOG_NB_TAGS=true
- CATALOG_MIN_BRANCHES=1
- CATALOG_MAX_BRANCHES=1
- TAGLIST_PAGE_SIZE=100
- REGISTRY_SECURED=false
- CATALOG_ELEMENTS_LIMIT=1000
container_name: registry-ui
registry:
image: registry:2
ports:
- 5001:5000
volumes:
- ./data:/var/lib/registry
environment:
REGISTRY_LOG_LEVEL: info
REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY: /var/lib/registry
REGISTRY_STORAGE_DELETE_ENABLED: true
OTEL_TRACES_EXPORTER: none
OTEL_METRICS_EXPORTER: none
Start the Registry¶
Open a dedicated terminal and run:
Open a second terminal and check containers:
Open the registry UI:
From another host on the same network, use:
Add the Registry to a VeeaHub¶
Run:
Expected output:
If the selected VeeaHub is a gateway node, the mesh units are updated.
List Insecure Registries¶
Run:
Expected output:
Remove an Insecure Registry¶
Run:
Confirm removal:
Expected output: