Last fix

.github/workflows/release.yml

@@ -5,7 +5,7 @@ on: pull_request
 #     branches:
 #       - "main"
 env:
-  PUBLISH_TO_GHCR_IO: true
+  PUBLISH_TO_GHCR_IO_IMAGE_URI: ghcr.io/jericop/inline-app:latest
 jobs:
   build:
     runs-on: ubuntu-22.04

README.md

@@ -8,10 +8,9 @@ It is heavliy inspired by the following article. While the article is invaluable
 
 * https://medium.com/buildpacks/unpacking-cloud-native-buildpacks-ff51b5a767bf
 
-
 ## Primary objective
 
-The primary objective is to create a Dockerfile that has all of the lifecycle commands needed to build and push architecture-specific images to a registry. `Dockerfile-example` is an example of how it works.
+The primary objective is to create a Dockerfile that has all of the lifecycle commands needed to build and push architecture-specific images to a registry. `Dockerfile-example` is an example of how it works. You can then combine the architecture-specific images into a manifest list (multi-arch) image.
 
 ## `pack-with-buildkit.sh`
 
@@ -29,4 +28,8 @@ This script will do the following:
 
 ## Requirements
 
-* Multi-arch builders are required. I'm using ones that I build and publish.
+* Multi-arch builders are required. I'm using ones that I build and publish.
+
+## Published image(s)
+
+* ghcr.io/jericop/inline-app:latest

pack-with-buildkit.sh

@@ -127,9 +127,9 @@ docker buildx imagetools create \
 
 crane manifest localhost:$registry_port/inline-app:latest  | jq
 
-if [[ ! -z "${PUBLISH_TO_GHCR_IO:-}" ]]; then
+if [[ ! -z "${PUBLISH_TO_GHCR_IO_IMAGE_URI:-}" ]]; then
   crane copy localhost:$registry_port/inline-app:latest ghcr.io/jericop/inline-app:latest
-  log_message "Published image to: ghcr.io/jericop/inline-app:latest"
+  log_message "Published image to: $PUBLISH_TO_GHCR_IO_IMAGE_URI"
 fi
 
 # This image can then be copied to another registry