How to avoid 6 minute gap in build?
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
GitHub
Failed to parse version => wastes 6 minutes of build time · Issue ...
[05:52:34 INFO] => Templating for recipe at ./recipes/recipe.yml [05:52:34 INFO] => Retrieving OS version from ghcr.io/ublue-os/aurora-dx-hwe:42 [05:52:39 DEBUG] => Successfully inspected ...
Solution:Jump to solution
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 `dock...2 Replies
Solution
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_optsI have plans to move over to using the
dagger-sdk which would allow far more complex build pipelines that would solve this issue