ArchitectureOverview
Docker, build and run
Two crates talk to Docker: one builds images and one controls containers.
To make an image, the engine calls ferry-build. This crate runs the git and docker commands.
1 / 3
ferryd does not run your apps itself. It tells the Docker daemon what to do, through the Docker Engine API and through the docker command.
The two crates
| Crate | Contents |
|---|---|
ferry-build | It changes source into an image: git fetch or archive extraction, runtime detection, and a Dockerfile for native runtimes. Then it runs docker build with BuildKit and sends the output to the deploy log. |
ferry-docker | A typed wrapper over the Docker Engine API (through bollard): containers, images, volumes, networks, logs, stats and exec. It knows nothing about services or deploys. |
Read more
- The build step of the deploy pipeline.
- Names and labels in Docker: how Ferry finds its own resources.
- Builds and runtimes, for the user view.