You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: BUILD.md
+6-17Lines changed: 6 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,25 +26,14 @@ Add the package you want to the appropriate `setup.sh` for example `heroku-24/se
26
26
+ libc6-dev
27
27
```
28
28
29
-
Once done, run `bin/build.sh` locally to generate the corresponding `installed-packages*` files. Multi-arch base images (heroku-24 and beyond) will produce an `installed-packages-$ARCH.txt` for each architecture, while single architecture images will produce a singular `installed-packages.txt`.
29
+
Once done, run `bin/build.sh` locally to generate the corresponding `installed-packages*` files. Multi-arch base images (heroku-24 and beyond) will produce an `installed-packages-$ARCH.txt` for each architecture.
30
30
31
31
The `*-build` variants include all the packages from the non-build variant by default. This means that if you're adding a package to both, you only need to add them to the non-build variant. The example above will add `libc6-dev` to both `heroku-24` and `heroku-24-build`.
32
32
33
-
The `*cnb*` variants (which only exist for heroku-22 and prior) inherit the installed packages from the non-`*cnb*` variant. Add packages to a non-`*cnb*` variant to add them to the `*cnb*` variant.
33
+
# Releasing Base Images
34
34
35
-
# Releasing Heroku Base Images
35
+
We use GitHub Actions to build and release the base images:
36
36
37
-
We use GitHub Actions to build and release Heroku Base Images:
38
-
39
-
* Any push to `main` will build the images and push the nightly Docker tag variants (such as `heroku/heroku:24-build.nightly`).
40
-
* Any new Git tag will build the image and push the latest Docker tag (such as `heroku/heroku:24-build`),
41
-
as well as a versioned tag (such as `heroku/heroku:24-build.v123`). The `arm64` images will then also be
42
-
converted to a Heroku-specific `.img` format and uploaded to S3 for consumption by the runtime hosts.
43
-
44
-
# Generating `.img` format Base Images locally
45
-
46
-
To test the generation of the Heroku-specific, amd64-only `.img` file:
47
-
48
-
1. Build the Docker images for your chosen stack as normal above.
3.`docker run -it --rm --platform=linux/amd64 --privileged -v /var/run/docker.sock:/var/run/docker.sock heroku-image-tools STACK_VERSION` (where `STACK_VERSION` is a integer version like `24`)
37
+
* Any push to `main` will build the images and push the nightly Docker tag variants (such as `ninech/deploio-heroku:24-build.nightly`).
38
+
* Any new Git tag will build the image and push the latest Docker tag (such as `ninech/deploio-heroku:24-build`),
39
+
as well as a versioned tag (such as `ninech/deploio-heroku:24-build.v123`).
0 commit comments