-
Notifications
You must be signed in to change notification settings - Fork 283
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 inspect
on an image created using an extension doesn't display swapped run-time base image
#1797
Comments
Hi @cormacpayne - thanks for reporting this issue. Just to confirm, is
|
One more question - is it possible to confirm your lifecycle version? Looking at the pack code, this seems to be reading from "old" metadata that might not getting updated in lifecycle 0.16.x but will be updated in lifecycle 0.17.x. |
@natalieparellano -- Hey Natalie, thanks for the prompt response! I'm seeing the run-time image being swapped as expected when running the application (i.e., my .NET app is able to run in a container even though the statically-defined run-time image in the builder that From right before the
I'll upgrade to a newer version of the lifecycle and see if the same |
Just a quick follow-up: I tested with the Happy to provide any additional information you may require 🙂 |
Ah, apologies - this is fixed in lifecycle on |
Perfect! Thanks for the update -- feel free to let me know when the latest tag containing the fix is available and I'll be happy to test it out on my side as well! |
@natalieparellano Hey Natalie, just a quick update on this item: I've been trying to use a builder created with the
What's interesting is that if I remove the
I was hoping to use |
@natalieparellano Thanks for your help with this! On top of @cormacpayne's question, I would like to know if you have visibility on when these changes would be released? |
This has been referenced in a community discussion at buildpacks/community#223 |
@cormacpayne @daniv-msft thanks for your question, and apologies for the slow reply - the notification was filtered from my inbox somehow.
All that is to say that, to your point, we need to get a new release of At this point all of the issues in the milestone now have a PR that is ready for review, so I think it's safe to assume that we're getting pretty close now. I'll follow up in the next couple of days when we have a better estimate. |
@natalieparellano Hey Natalie, thanks for the informative response as always -- I just tested our flow with the
It looks like we should be good to go whenever this version of Thanks for all of the help! |
Hi @cormacpayne Regarding the pack release cadence, we don’t have a time-based release cadence anymore, now we do a feature-based release cadence for minor releases, so the time between releases could be longer. We are aiming for time-based patch versions with bug fixes and dependency bumps (but we haven’t been great at sticking to this). We are trying to grow the platform team and have more things done, but it's been a little tricky. In any case, we are very close to releasing pack 0.30.0 |
This issue will close once pack 0.30.0 is released |
Closing after pack 0.30.0 released |
Description
I have a set of buildpacks that use the same skeleton base image as the build and run-time stack, but depending on the platform found to be used by the provided source (i.e., .NET, node, Python, etc.), the platform's buildpack will use a corresponding extension to swap out the run-time base image to one based on that platform.
For example, the run-time stack specified in the builder is
skeleton-run-image:123
, and when our .NET buildpack is used, it will leverage an extension that swaps out this run-image withdotnet-run-image:123
. However, when I runpack inspect
on the image produced frompack build
, I see the following:Proposed solution
Using the above example, I would've expected the swapped out run-image,
dotnet-run-image:123
to be the displayed "Run Images" when callingpack inspect
.Describe alternatives you've considered
I'm not sure of other routes to take when attempting to determine the run-time image used for an image produced by
pack build
-- I'm not sure if this "Run Images" field is determined by the static run-time image provided either within the builder or with the value provided to the--run-image
argument. I was hoping there would be a way for the builder to parse the new run-time image from the extension and update the metadata used bypack inspect
to reflect the swap.Additional context
Please feel free to let me know if you need any additional information from me! Thanks in advance!
The text was updated successfully, but these errors were encountered: