Error Using Extensions in Ubuntu Jammy: "stat /cnb/lifecycle/extender: no such file or directory: unknown" #1979
Comments
a1flecke
added
status/triage
|
@a1flecke thanks for this - this is an interesting one. In your successful build log output, do you ever see log lines with prefix |
natalieparellano
added
status/ready
|
Potentially related: #850 Possible solution: we could create an "ephemeral" run image (similar to an ephemeral builder) to use for run image extension. This image would be the run image + the lifecycle binary layer from the lifecycle image. This is the right way to do it anyway. Presently we copy the |
Yes I saw some. Here are some of them: |
|
Thanks for this - I think it's what I suspected, and we can fix it without monumental effort. I'll try to take a look in the next few days. |
|
@natalieparellano any ETA on this? Any more information needed? |
|
@a1flecke apologies, I've been out unexpectedly and slow to pick this up. It's still on my list, but if anyone else has cycles to push it forward faster I can try to offer some guidance. |
|
@natalieparellano Any updates? Is there a way that I could help here? I will be new to Go and the code base, but I learn quickly, especially if I have an example to follow. |
|
@a1flecke - apologies for the slow reply. I'll update this issue shortly with some breadcrumbs... |
|
@a1flecke I started to write out some notes here, but due to edge complexity I found it easier to just write out all the changes in code 😅 - could you take a look at #2007? There are currently some (unrelated) issues with CI but you could build pack locally with |
|
@natalieparellano Assuming that I followed the Golang correctly, it makes sense. I do not currently have Go setup. I may need to do that as we currently have 2 needs for extending buildpacks on the run image side |
|
Artifacts can be found here: https://github.com/buildpacks/pack/actions/runs/7268122189?pr=2007 |
|
@a1flecke let me know if you managed to check the binaries with the fix |
|
@natalieparellano @jjbustamante sorry for the slow response. We have confirmed that this change worked. |
Summary
Using pack with extensions fails in Ubuntu Jammy with "stat /cnb/lifecycle/extender: no such file or directory: unknown". It succeeds locally on Mac OS.
If it matters, the Ubuntu Jammy is container running on an Ubuntu Focal host.
Reproduction
Steps
cd use-dockerfile-extension./try-pack.sh paketobuildpacks/builder-jammy-full ${ANOTHER_DOCKER_URI}try-pack will re-tag the original builder with ${ANOTHER_DOCKER_URI} to allow extension use on a trusted builder. The script will also push the retag to the docker registry to account for pack wanting to pull the image as part of its code path.Current behavior
Fails:
Expected behavior
I expected pack to succeed in Ubuntu Jammy as it did with MacOS:
Environment
pack info
Failing scenario:
passing scenario:
docker info
failing scenario:
passing scenario:
The text was updated successfully, but these errors were encountered: