-
Notifications
You must be signed in to change notification settings - Fork 7
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
Investigate docker build issue on linux/arm64 platform #846
Comments
Builds now started passing on |
There is no reason not to use a more recent version of go to build the binary in docker images. This should also reduce the chances of random segmentation fault when building for arm64 platform. Fixes #846
IMO it looks like the VM is running out of RAM and causing some weird behavior. It looks like I've found a workaround, as I've commented in my issue: jobs:
build:
runs-on: ubuntu-22.04 Please try like that and let me know if it helps. :) |
There is no reason not to use a more recent version of go to build the binary in docker images. This should also reduce the chances of random segmentation fault when building for arm64 platform. Fixes #846
Thank you @FacuM, I'll give that a shot 👍 |
@FacuM In our case using the ubuntu-22.04 runner image made no difference. See: https://github.com/filecoin-project/go-f3/actions/runs/13007480659/job/36277473006?pr=855 |
With QEMU setup it still fails: https://github.com/filecoin-project/go-f3/actions/runs/13013844154/job/36297943821 |
Update using qemu v8 works. |
Initially observed in #834 but it is unrelated to the changes in that PR: confirmed by re-running the docker build on latest commit of
main
here. The issue:Why has it started failing now?
Because go-f3 container build is not reproducible:
latest
tags for the build and base images.Change at any of the above layers could have caused the issue, e.g. gcc linker upgrade.
Also, yesterday GitHub Actions was having a bad day with a flurry of errors specifically in docker build jobs which may be related.
Building multi-platform containers locally (using
podman
) passes for me with no issues.Unblocking the merge of that PR by capturing this issue to investigate the problem separately.
The text was updated successfully, but these errors were encountered: