Deploy to Ignite

Goal: an image you pushed to Dodil Registry, running as an Ignite app. Ignite’s prebuilt image mode (--image-ref) skips the build step entirely — the registry is the source of truth.

1. Push the image

Follow the Quickstart if you haven’t:


docker tag web:1.2.0 registry.dodil.io/acme/web:1.2.0
docker push registry.dodil.io/acme/web:1.2.0

Check the scan report before deploying: dodil registry vuln web 1.2.0.

2. Give Ignite a pull credential

Private repository (the default) → Ignite needs credentials to pull. Issue a key and store it as an Ignite registry secret:


dodil auth apikey issue --name ignite-pull --role registry.developer --service registry


dodil ignite secret create dodil-registry \
  --type registry \
  --username ci \
  --password dk_... \
  --server-address registry.dodil.io

The username is arbitrary (the registry authenticates on the dk_ password); --server-address must match the registry host in your image ref. Skip this whole step if the repository is public — anonymous pulls need no secret.

3. Deploy

One command creates the app, registers the prebuilt image, and publishes a version (no build phase for --image-ref):


dodil ignite app deploy acme:web \
  --image-ref registry.dodil.io/acme/web:1.2.0 \
  --registry-secret-ref dodil-registry \
  --tier small

The app id is <org>:<app>. --registry-secret-ref names the secret from step 2.

4. Verify


dodil ignite app get acme:web
dodil ignite app state acme:web
dodil ignite app logs acme:web

5. Roll out a new version

Push a new tag, then re-deploy pointing at it:


docker push registry.dodil.io/acme/web:1.3.0
dodil ignite app deploy acme:web --image-ref registry.dodil.io/acme/web:1.3.0 --registry-secret-ref dodil-registry

Pin immutable, versioned tags (1.3.0) rather than latest — Ignite versions then map one-to-one to registry artifacts, and dodil ignite version rollback returns you to a known digest.

For app tiers, env vars, scaling, and everything else on the Ignite side, see the Ignite docs .