Error when using the new multi-arch Paketo buildpacks about spring-boot

[ThomasVitale]

@mhalbritter yes, the failure on GitHub Actions (Ubuntu 22.04) and GitHub Codespaces (Ubuntu 20.04) is reproducible and happens consistently.

[mhalbritter]

It works on my machine, though. Both projects work fine with g bootBuildImage.

Env:

> docker version
Client: Docker Engine - Community
 Version:           26.1.2
 API version:       1.45
 Go version:        go1.21.10
 Git commit:        211e74b
 Built:             Wed May  8 14:01:38 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          26.1.2
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.10
  Git commit:       ef1912d
  Built:            Wed May  8 13:59:55 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.31
  GitCommit:        e377cd56a71523140ca6ae87e30244719194a521
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

> uname -a
Linux workstation 6.8.9-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May  2 18:44:19 UTC 2024 x86_64 GNU/Linux

log.txt

[ThomasVitale]

Thanks @mhalbritter for the feedback. I've done some more testing. I have tried the following scenarios and they all worked fine, based on Docker Desktop 4.30.0 (Docker Engine 26.1.1).

• macOS (ARM64)
• Windows 10 (AMD64)
• Ubuntu 22.04 on WSL2/Windows 10 (AMD64)

I get the error in the following scenarios. I wonder if it's something related to the older Docker version or something specific to the VM images used by GitHub.

• ubuntu-22.04 GitHub Runners using Docker Engine 24.0.9 (example: https://github.com/ThomasVitale/supply-chain-security-java/actions/runs/9038631465/job/24840127488). Runner configuration: https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md
• Ubuntu 20.04 on GitHub Codespaces using Docker Engine 24.0.9 (it can be tested from this repo: https://github.com/ThomasVitale/buildpacks-demo).

[mhalbritter]

Thanks for the feedback. The failures on CI are reproducible, and not some flaky internet connection, right?

[ThomasVitale]

I also tried the build on newer GitHub runners (Ubuntu 24.04, Docker 26.1.0) and the outcome is the same: the build hangs indefinitely. Example: https://github.com/ThomasVitale/supply-chain-security-java/actions/runs/9059907830/job/25092379764