Builds

Docker Manager builds images from a Git repository on one of your servers. The image stays on that server, where a stack can use it right away. It is not pushed to a registry.

Build an imageCopy Anchor Link

1. Open Builds and press Build Image.
2. Pick the Environment to build on.
3. Enter the Repository URL (HTTPS) and, if needed, the Branch, Tag or Commit. Empty uses the repository's default branch.
4. Check the Image Names. Docker Manager suggests one from the repository and branch, for example myapp:main; change it or add more, one per line.
5. Under Advanced you can set the folder, the Dockerfile, the target stage, the platform and build arguments, or build without the cache.
6. Press Build Image and follow the output.

To build a pull request, paste its link from GitHub, GitLab, Forgejo or Gitea into Repository URL. Docker Manager fills in the repository and the pull request and builds its latest commit, also from a fork; build again to pick up new commits. Only build pull requests you trust: the build runs their Dockerfile on your server.

For a private repository, add a credential under Registries → Git Credentials first. The Git Credential field then picks the matching one.

Follow your buildsCopy Anchor Link

The top of Builds → History shows the last build, the success rate, the builds that failed in the last 7 days and how long a build typically takes. Click a figure to see the builds behind it. The list holds the newest 200 builds of each environment; its summary says how many there are in all.

A running build shows its progress above the list, also after you reload the page. Cancel stops it; layers built so far stay in the build cache.

The ⋯ menu of a build opens the build, its image or its job, builds it again, saves it as a build definition and, while it runs, offers Cancel Build. A build's page links its repository and, on GitHub, GitLab, Gitea, Forgejo and Codeberg, the commit and the pull or merge request it built. Copy Image Name beside each of its Image Names copies the name with its tag, ready for the image: line of a Compose file. Below its output, Other Builds lists the builds of the same definition or repository.

Build againCopy Anchor Link

• Build Again repeats a finished build. If it used build arguments, the form opens filled in and you type their values again.
• Edit and Build Again opens the form filled in from the build, so you can change something first.
• Save as Build Definition keeps its settings on the Definitions tab, so you can start it again any time. Type the build argument values once; the definition keeps them.
• On Definitions, Last Build shows how each definition's last build went, and View Builds in its ⋯ menu lists all its builds.

To build a stack's own images, use Build on the stack. Prune Build Cache on the Builds page frees disk space (see Maintenance).