-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pack build
fails to export image if extension run image not previously pulled
#1804
Comments
@cormacpayne - thanks for this. This appears to be the same issue as #1686, which should be fixed on pack 0.30.0-pre.2 - can you confirm the version you are using? |
@natalieparellano shoot, not sure how I missed the existing issue (GitHub search filters strike again 😢) -- I just updated to the
I'm happy to provide any additional information or try any other versions of the tools involved! |
Ah, apologies @cormacpayne - I may have steered you wrong. It appears that pack I suspect the output from above may still be from an older version of pack, because I see
This particular bug will be fixed in #1789 and together with a couple of other fixes (cc @jjbustamante) we hope to cut a new pre-release in the next few days. In the meantime, I tried to repro the above using lifecycle
Is it possible to check if you have |
@natalieparellano thanks for the detailed response -- it is greatly appreciated! The I just cleared the Docker images and cache on my system and did a fresh Logs
|
@cormacpayne - that's very interesting. If you run
Perhaps the |
@natalieparellano ah ha, I found the culprit thanks to the I just ran through this scenario with the updated builder and we're all good now -- the extension run image is being pulled down after a wipe of the Docker images and cache! Sorry for the false alarm, and thanks again for all of the help! 😃 |
That's great to hear! 🙌🏼 |
Description
When using
pack build
to create an application image using a builder containing various platform buildpacks and their corresponding build and run extensions, it seems that if the new run image base (from the run extension) wasn't previously pulled down on the machine, then the application image cannot be exported.Below are the verbose logs from the export phase where the new run image base has not been pulled down onto the machine:
If I then use
docker pull
to pull down the new run image specified in the extension, the application image is exported successfully:Proposed solution
Using the same daemon that can pull down the
buildpacksio/lifecycle
, builder and stack images if not present on the machine, the new run image defined in the extension would also be pulled down if not present.It appears that the exporter already has context about what this new run image is via the logs above:
So I was hoping the daemon could check if this image is present locally first before proceeding.
Describe alternatives you've considered
We could manually pull down the run image before running
pack build
, but we'd have to ensure that all possible run images bundled as extensions within the builder are present since we won't know which platform a user is targeting when using the builder until the buildpacks decide.Additional context
The text was updated successfully, but these errors were encountered: