dcloud ecr pull-through-cache create

Mirror an upstream registry under a prefix

IAM ecr:CreatePullThroughCacheRuleChanges state

Then `docker pull <org>.ecr.<root>/<prefix>/<name>:<tag>` fetches <name> from the upstream on first pull and serves it from this registry after that (Docker Hub official images: `<prefix>/node` = `library/node`). Tags are re-checked upstream after 6 hours; when upstream fails, the cached copy is served. Bringing new images in needs ecr:BatchImportUpstreamImage. upstreamRegistry: docker.io, ghcr.io, quay.io, registry.k8s.io, public.ecr.aws, mcr.microsoft.com. A login (username + passwordSecretId, a Deutsche Cloud Secret granted to the `registry` consumer) raises Docker Hub's anonymous pull limit and reaches private upstream images.

Synopsis

dcloud ecr pull-through-cache create --prefix prefix --upstream-registry upstreamRegistry [flags]

Flags

  • --prefixRequired

    string

    The path images are pulled under, e.g. dockerhub: <prefix>/<name> mirrors <name> upstream. 2–64 characters of lowercase path components (letters, digits, . _ - inside, / between). A prefix another rule has is refused with 409

    Constraints: 2-64 chars, /^[a-z0-9]+(?:[._-][a-z0-9]+)*(?:\/[a-z0-9]+(?:[._-][a-z0-9]+)*)*$/

  • --upstream-registryRequired

    enum

    The registry mirrored: docker.io, ghcr.io, quay.io, registry.k8s.io, public.ecr.aws or mcr.microsoft.com

    One of: docker.io, ghcr.io, quay.io, registry.k8s.io, public.ecr.aws, mcr.microsoft.com

  • --usernameOptional

    string

    Upstream user name, 1–255 characters; given together with passwordSecretId or not at all. Omitted: anonymous pulls

    Constraints: 1-255 chars

  • --password-secret-idOptional

    string

    Id of a Secret of this organization holding the upstream password or token, granted to the registry consumer; given together with username. An id that names no secret is refused with 400

Example

dcloud ecr pull-through-cache create --prefix example --upstream-registry docker.io

Generated from the API description, the same one the API checks requests against and the CLI is built from.