Skip to content

Sandboxes · 17 November 2026

Import a private image by its digest

POST /v2/images takes image as repo@sha256:<64 hex digits> with pullSecret, the name of a hidden secret that holds the registry login (header Authorization, format Basic {value}, hosts the registry's token service). Runtime's egress proxy signs in to the registry for the build itself. It asks only for a token that pulls the named repository, and adds that token only to the build machine's pulls by digest. The build machine never holds the login or the token, does not use a registry mirror for the image, and accepts no exec, file, link or fork call while it builds. The proxy checks the secret again at each sign-in: it must be hidden, be a login for that registry, and have a scope that reaches no machine. Registry logins moved from 1.0 are stored this way as REGISTRY_<host>.

Same day.

Cut your cloud billby 66%.

7 days of Pro for $0, and no card to sign up. Billed by the second after.

Start your free trial