[17:24:33  INFO] => Retrieving OS version from ghcr.io/ublue-os/aurora-dx-hwe:42
[17:24:36 DEBUG] => Successfully inspected image ghcr.io/ublue-os/aurora-dx-hwe:42!
[17:24:36  WARN] => Failed to parse version:
Failed to deserialize version latest-42.20250627.2
[17:24:36  WARN] => Unable to get version via image inspection due to error:
  × Failed to parse version from metadata for ghcr.io/ublue-os/aurora-dx-
  │ hwe:42
[17:24:36  WARN] => Pulling and running the image to retrieve the version. This will take a while...
[17:30:16 DEBUG] => Successfully inspected image ghcr.io/blue-build/cli/build-scripts:7828e7872b342d05302417db1bd94bf93d347383!
[17:30:16 DEBUG] => Using build scripts image: ghcr.io/blue-build/cli/build-scripts:7828e7872b342d05302417db1bd94bf93d347383

Has anyone been able to avoid this 6 minute delay? It seems like it wants to avoid it, but fails to find what it is looking for. How can I help it to find the version it needs? Also reported here: https://github.com/blue-build/github-action/issues/86

message has been deleted

Unfortunately, this is becuase upstream is changing the version string on the

LABEL

. We've had several people come and complain, but the reality is that if the

LABEL

on the image doesn't set the version properly, then we have to get that information from within the image which requires downloading it and running it. For docker builds, we make use of

buildx

which is a builder that runs in a container and unfortunately the docker frontend doesn't allow us to run arbitrary commands like

docker run

does. If you build with podman it will be quicker since the builds and container runs use the same container-store. You can add the

-B podman

arg via the action using [build_opts](https://blue-build.org/reference/github-action/#build_opts-optional)