-
Notifications
You must be signed in to change notification settings - Fork 40.8k
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
Cannot package OCI image when 'docker.io/paketobuildpacks/new-relic' is provided as a buildpack #43126
Comments
Does this work when building the image with |
@mhalbritter, yes, running this command in the root of my reproducer repository works: |
Possibly related to #39323 (comment) |
docker.io/paketobuildpacks/new-relic
is provided as a buildpack.
We have a couple of issues causing this. The first is that we don't support nested index (as documented here). The second is the media type seems to have changed in the manifest from |
Update `ExportedImageTar.IndexLayerArchiveFactory` to support nested indexes. Nested indexes support a layer of interaction where the `index.json` file points to a blob that contains the read index to use. Prior to this commit, we only supported indexes provided directly by the `index.json` file. This missing support results in "buildpack.toml: no such file or directory" errors when referencing specific buildpacks and using Docker Engine 27.3.1 or above. See gh-43126
Spring Boot version: 3.2.6.
Docker Engine version: 27.3.1.
When running Spring Boot Gradle Plugin's
bootBuildImage
task while providing the alternate set of buildpacks below, I observe a failure. Reproducer: https://github.com/RobertoGraham/spring-boot-buildpack-bug/tree/31900583887eb0a05730d89b50a1acaecb9eb822.The text was updated successfully, but these errors were encountered: