Skip to Content
We are live but in Staging 🎉
Quickstart

Quickstart

Push your first image to Dodil Registry with plain docker. No repository setup needed — the repository is created by the push itself.

Before you start

  • The dodil CLI, installed and authenticated — see Install the CLI . Run dodil auth login once.
  • Docker (or podman) locally, and an image to push. Examples below use your-org — substitute your organization name.

1. Issue an API key

docker login authenticates with a dk_ API key as the password:

dodil auth apikey issue --name my-laptop --role registry.developer --service registry
API key issued:
  lookup:    ak_...
  principal: sa-... (serviceAccount)
  secret:    dk_...

Save the secret now — it is shown once. (Add --ttl 720h for an expiring key; --drn scopes it to specific resources.)

2. Log in

docker login registry.dodil.io

Username can be anything (e.g. ci); the password is the dk_ secret from step 1.

3. Tag & push

docker tag your-image:latest registry.dodil.io/your-org/your-image:latest
docker push registry.dodil.io/your-org/your-image:latest

The image reference is always <host>/<org>/<repo>:<tag>. The push creates the your-image repository if it doesn’t exist — private by default.

4. See it in the console (and the CLI)

The repository now shows up on the Registry page of the Dodil console, with artifact count, pull count, and a scan badge once the CVE scan completes. From the CLI:

dodil registry repo list
dodil registry artifact list your-image
REPOSITORY   ARTIFACTS  PULLS  VISIBILITY
your-image   1          0      private

DIGEST              TAGS    SIZE     SCAN
sha256:4f5c2a8b91d2 latest  52.4 MB  None

5. Pull it back

dodil registry pull-command your-image latest

prints the exact command:

docker pull registry.dodil.io/your-org/your-image:latest

6. Read the scan

Every push triggers a vulnerability scan:

dodil registry vuln your-image latest
scan: Success   severity: Low   total: 3   fixable: 1

Next

OverviewCore Concepts