---
# nocheck: dynamic-flag
node:
  enabled: true
  shared: true
  bond: 1
cache:
  healthcheck:
    flavor: wget
    port_key: registry
    path: v2/
  modes:
    compose:
      enabled: true
    swarm:
      enabled: false
  # nocheck: default-placement-manager  pull-through cache backs docker stack deploy; chicken-and-egg if scheduled on a worker that still needs to pull custom images from it
  placement: manager
  enabled: true
  shared: true
  bond: 1
  image: registry
  version: "3"
  name: cache-registry
  min_storage: 221MB
  backup:
    disabled: true
  cpus: "0.5"
  mem_reservation: 128m
  mem_limit: 512m
  pids_limit: 256
  ports:
    local:
      registry: 5001
    internal:
      registry: 5000
    onion:
      # nocheck: onion-flag  the pull-through mirror exists to serve this node's own image pulls; publishing it would relay Docker Hub for strangers
      registry: false
  proxy:
    remote_url: "https://registry-1.docker.io" # nocheck: url
  lifecycle: beta
# nocheck: dynamic-flag - pull-through cache content is re-fetchable, the backup consumer stays permanently off
container_backup:
  enabled: false
  shared: true