Pushing your own images

bootload runs a private container registry at registry.bootload.io. Push your own images to it and deploy them straight onto the platform — no public Docker Hub repo required. Images live in your organization's namespace, are pulled over the private network at deploy time, and are billed as storage at €0.20 per GB-month.

Log in

The CLI mints a short, scoped token and hands it to Docker for you:

bootload image login

This runs docker login registry.bootload.io under the hood — the token only carries registry:push/registry:pull, never your full session, and it goes in on stdin, never on the command line.

Push an image

bootload image push myapp:v1

That tags your local myapp:v1 as registry.bootload.io/<your-org>/myapp:v1 and pushes it. Pass --as name:tag to publish under a different name. When it's done the CLI prints the exact deploy command:

bootload deploy --image registry.bootload.io/<your-org>/myapp:v1

You can also pick a pushed image from the Hub push step of the deploy wizard in the portal.

See what you've pushed

bootload image list

Your pushed images also appear under resources → hub images in the portal.

Delete an image

Images keep accruing storage billing until you remove them, so clean up tags you no longer need:

bootload image delete myapp:v1

or use the delete button on the resources → hub images card. A delete is refused while any service still deploys that image — scale the service to zero or roll it to another image first — so you can't accidentally pull a running app's image out from under it. Once deleted, the image stops counting toward your storage bill.

Private registries elsewhere

To pull from a third-party private registry (GHCR, a corporate registry) instead of pushing to ours, store read-only credentials with bootload registry add (or resources → external registries) and deploy from that registry's image ref directly.