Split build-container-image into build-container-image-{debug,release}

This allows `run-in-container` to default to using the much faster
`build-container-image-debug`.
This commit is contained in:
Slavi Pantaleev
2024-09-21 14:18:28 +00:00
parent 2a5a2d6a4d
commit c8c5e0e540
3 changed files with 32 additions and 8 deletions

View File

@@ -15,8 +15,16 @@
We provide prebuilt container images for the `amd64` and `arm64` architectures, so **you don't necessarily need to build images yourself** and can jump to [Running in a container](#-running-in-a-container).
If you nevertheless wish to build a container image yourself, you can do so by running `just build-container-image`.
This will build and tag your container image as `localhost/baibot:latest`.
If you nevertheless wish to build a container image yourself, you can do so by running:
- (recommended) `just build-container-image-release` to build a release version of the container image
- or `just build-container-image-debug` to build a debug version of the container image
Debug images are faster to build but are larger in size.
Release images are ~5x smaller in size, but are slower to build.
Both of these commands will build and tag your container image as `localhost/baibot:latest`.
### 🐋 Running in a container