Docker on Unbroker

Deploy a container

A Dockerfile is a useful boundary between your application’s runtime requirements and the platform that runs it. Unbroker supports that boundary: you define the container, and Cloud provides the service, deployment history and operating controls around it.

Use this path for applications with custom system packages, a deliberate runtime image or an existing container-based release process.

Choose where the build happens

Build from your repository

Connect the source repository and select its Dockerfile. Unbroker builds the image from that source and makes the build output available with the deployment.

Deploy a prebuilt image

If your CI system already produces the release artifact, create an image service from the registry reference. Keep a release-specific tag or digest so the deployed version is identifiable.

Configure databases, secrets and storage

Connect the service to a database, configure runtime secrets and add a public domain on Pro. When the application needs durable local files, attach a persistent volume and configure a backup destination.

Unbroker’s project view keeps these components together. Use Cloud to see the services, or ubctl and the agent skill to inspect and operate them from your coding workflow.

Test locally, then deploy

The Docker tutorial provides a minimal image and local run check, then explains the source-build and image-service options. It also covers the port, storage and configuration boundaries that determine whether a container is ready to serve real traffic.

Bring your existing image or start from the example, then use the same operational workflow as you add the rest of the application.