Pull

Pull

pocker pull pulls OCI images from registries into pocker's local cache. By default, it imports the final image into Docker.

Pull one image into Docker:

pocker pull alpine:latest

Pull several images:

pocker pull alpine:latest busybox:latest

Download into pocker's cache without importing into Docker:

pocker pull --no-load alpine:latest

Pull a specific platform:

pocker pull --platform linux/arm64 ghcr.io/example/app:latest

Pull more than one image at a time:

pocker pull --max-parallel-images 4 alpine:latest busybox:latest

Increase layer download concurrency:

pocker pull --max-parallel-downloads 8 ghcr.io/example/app:latest

Increase blob retries on unstable links:

pocker pull --blob-retries 32 ghcr.io/example/app:latest

Retry retryable registry and blob failures indefinitely:

pocker pull --retry-forever ghcr.io/example/app:latest

Increase registry request retries for connection, pre-response, and retryable HTTP failures:

pocker pull --request-retries 16 ghcr.io/example/app:latest

Pull a private image with explicit credentials:

printf '%s' "$REGISTRY_PASSWORD" | \
  pocker pull \
    --username my-user \
    --password-stdin \
    ghcr.io/example/private-image:latest

If explicit credentials are not supplied, pocker tries to use Docker's registry auth configuration.

Pull through a pocker cache server:

pocker pull --cache-from http://cache.example:5000 alpine:latest

By default, cache misses fall back to the upstream registry. Require all content to come from the cache server:

pocker pull --cache-from http://cache.example:5000 --cache-only alpine:latest

The cache server sees normalized upstream image paths, so alpine:latest is served through a path like cache.example:5000/registry-1.docker.io/library/alpine:latest.