v0.0.101 broken: lifecycle 0.21.2 causes "No such image" crash during export

[Laffs2k5]

Expected Behavior

Building an application with paketobuildpacks/builder-noble-java-tiny:latest should complete all lifecycle phases (DETECTING, ANALYZING, RESTORING, BUILDING, EXPORTING) successfully and produce a Docker image.

Current Behavior

Builder v0.0.101 (released Feb 12 2026) crashes during the lifecycle EXPORTING phase with exit code 62:

ERROR: failed to export: saving image: failed to fetch base layers: saving image with ID "sha256:776f47ea..." from the docker daemon: No such image: sha256:776f47ea...

v0.0.101 bumps the lifecycle from 0.21.1 to 0.21.2. All other components are identical to v0.0.100, which works correctly.

Version	Lifecycle	Buildpacks	Run image	Result
v0.0.100	0.21.1	identical	ubuntu-noble-run-tiny:0.0.53	Works
v0.0.101	0.21.2	identical	ubuntu-noble-run-tiny:0.0.53	Crashes

Possible Solution

Revert lifecycle to 0.21.1 and release a new builder version, or wait for a lifecycle patch release that fixes the export regression.

I have filed a separate issue on buildpacks/lifecycle for the upstream regression in lifecycle 0.21.2:
buildpacks/lifecycle#1605

Steps to Reproduce

1. Use paketobuildpacks/builder-noble-java-tiny:latest (currently resolving to v0.0.101)
2. Build any Spring Boot application with mvn spring-boot:build-image (or pack build)
3. Observe DETECTING, ANALYZING, RESTORING, and BUILDING phases complete successfully
4. EXPORTING phase crashes with the "No such image" error

Reproducible across multiple runs on different self-hosted GitHub Actions runners.

Environment:

• Spring Boot 3.5.10 (spring-boot-maven-plugin:3.5.10)
• Java 21
• Docker on Linux (self-hosted GitHub Actions runners)
• Run image: paketobuildpacks/ubuntu-noble-run-tiny:0.0.53

Workaround: Pin to the v0.0.100 digest:

paketobuildpacks/builder-noble-java-tiny@sha256:cab14ec30d8175478dbbeacdc7db254add8604dec8ee47b432a53121b9032558

Motivations

Anyone using :latest (which currently resolves to v0.0.101) is affected. This includes users of spring-boot:build-image where builder-noble-java-tiny is the default builder for Java 21 in Spring Boot 3.5.x. Our CI/CD pipelines are completely blocked until we pin to an older digest.

[dmikusa]

There's very little that we can do about this since what you're saying points to an issue with the lifecycle binary. I will keep an eye on the issue you opened with the upstream project and when they release a fix we'll pick that up ASAP.

In the meantime, if this is impacting you:

1. Please 👍 this issue and the upstream issue, so we can get a sense of the impact.
2. Please pin your builder version to paketobuildpacks/builder-noble-java-tiny:0.0.100.

[mpo22]

My temporary workaround is to first pull the https://hub.docker.com/layers/paketobuildpacks/ubuntu-noble-run-tiny/0.0.53 image by Manifest Digest

docker pull paketobuildpacks/ubuntu-noble-run-tiny@sha256:776f47ea1aff1bce4ada111ab52e32edb72aefb88a84274b3cd5f0b919f51ce8

[dmikusa]

I've downgraded the Java builders to use 0.21.1.

• https://github.com/paketo-buildpacks/builder-jammy-java-tiny/releases/tag/v0.0.93
• https://github.com/paketo-buildpacks/builder-noble-java-tiny/releases/tag/v0.0.102

The other builders are being downgraded as well, that's in progress.

---

** UPDATE **

• https://github.com/paketo-buildpacks/builder-jammy-tiny/releases/tag/v0.0.442
• https://github.com/paketo-buildpacks/ubuntu-noble-builder/releases/tag/v0.0.79
• https://github.com/paketo-buildpacks/builder-jammy-base/releases/tag/v0.4.542
• https://github.com/paketo-buildpacks/builder-jammy-full/releases/tag/v0.3.590

All are updated.

[DarkAtra]

Hey @dmikusa, it seems like rolling back to version 0.0.100 does not resolve the issue for arm builds:

Pulling builder image 'docker.io/paketobuildpacks/builder-noble-java-tiny:0.0.100' for platform 'linux/arm64' 100%
[INFO]  > Pulled builder image 'paketobuildpacks/builder-noble-java-tiny@sha256:cab14ec30d8175478dbbeacdc7db254add8604dec8ee47b432a53121b9032558'
[INFO]  > Pulling run image 'docker.io/paketobuildpacks/ubuntu-noble-run-tiny:0.0.53' for platform 'linux/arm64' 100%
[INFO]  > Pulled run image 'paketobuildpacks/ubuntu-noble-run-tiny@sha256:33b7be8544b84524ed681323bd68cde16c808800bc5b7adb5d19ed3f24d1deb1'
[INFO]  > Pulling run image 'docker.io/paketobuildpacks/ubuntu-noble-run-tiny@sha256:3553c27d0e2262b61c191e34bc9488f9bf5bd5590865699dba8e5e09db8fc555' for platform 'linux/arm64' 100%
[INFO]  > Pulled run image 'paketobuildpacks/ubuntu-noble-run-tiny@sha256:3553c27d0e2262b61c191e34bc9488f9bf5bd5590865699dba8e5e09db8fc555'
[INFO]  > Executing lifecycle version v0.21.1
[INFO]  > Using build cache volume 'pack-cache-c3bc6ed4d0fc.build'
[INFO] 
[INFO]  > Running creator
[INFO]     [creator]     ===> ANALYZING
[INFO]     [creator]     Image with name "docker.io/paketobuildpacks/ubuntu-noble-run-tiny@sha256:3553c27d0e2262b61c191e34bc9488f9bf5bd5590865699dba8e5e09db8fc555" not found
[...]
[INFO]     [creator]     ===> EXPORTING
[INFO]     [creator]     ERROR: failed to export: get run image top layer SHA: image has no layers
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  03:36 min
[INFO] Finished at: 2026-02-16T19:06:00Z
[INFO] ------------------------------------------------------------------------
Error:  Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:3.5.9:build-image (default-cli) on project my-fancy-project: Execution default-cli of goal org.springframework.boot:spring-boot-maven-plugin:3.5.9:build-image failed: Builder lifecycle 'creator' failed with status code 62 -> [Help 1]
Error:  
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
Error:  
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
Error: Process completed with exit code 1.

We're using docker version 29.2.1 and i have the suspicion that it's related to that somehow. We'll try rolling back to an even older version for now.

[dmikusa]

@DarkAtra The upstream lifecycle project has a new release that looks like it's going to fix at least some of the issues. My local testing went well and it fixed the two issues I was able to recreate. That should come through the builders soon.

That said, we also saw some issues in pack itself.

• Spurious "failed to find a lifecycle binary for requested architecture" warning when using amd64 buildpacks/pack#2528
• Another containerd issue buildpacks/pack#2527

It's possible that there will be similar issues in Spring's implementation as well. We'll have to see as things get fixed.

That said, in all cases I've see the problem has been caused by containerd and Docker 29 defaulting to use containerd. If you disable containerd, that has fixed all of the issues that I've seen and that we've encountered in our own pipelines.

You can add a step into your GHA pipeline that disables it like this. It's quick & runs fast. Then you get the pre-Docker 29 behavior & things seem to just work.

     - name: Disable containerd snapshotter
        run: |
          echo '{"features": {"containerd-snapshotter": false}}' | sudo tee /etc/docker/daemon.json
          sudo systemctl restart docker

[DarkAtra]

Hey @dmikusa, thank you for your quick response! It seems like disabling containerd does not solve our issue. I've managed to build a reproducer: https://github.com/DarkAtra/paketo-docker-29-arm-issue (Java 21, Spring Boot 3.5.9 and Docker 29.2.1, builder-noble-java-tiny 0.0.102).

There are two build attempts:

• the first one uses docker 29.2.1 without disabling containerd. docker is setup via https://github.com/docker/setup-docker-action. This one successfully builds the amd version of the image but fails to build for arm.
• the second one disables containerd via daemon-config: '{"features": {"containerd-snapshotter": false}}'. This one fails for both amd and arm (with the same error message).

I'm kinda out of ideas. It seems to me like the run image (docker.io/paketobuildpacks/ubuntu-noble-run-tiny@sha256:3553c27d0e2262b61c191e34bc9488f9bf5bd5590865699dba8e5e09db8fc555 in our case) was successfully pulled but for some reason, the creator still fails with Image with name "docker.io/paketobuildpacks/ubuntu-noble-run-tiny@sha256:3553c27d0e2262b61c191e34bc9488f9bf5bd5590865699dba8e5e09db8fc555" not found.

Any hint or idea is very much appreciated.

[Laffs2k5]

FYI: our issues have been resolved, thanks