-
Notifications
You must be signed in to change notification settings - Fork 539
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
Build summary generation failing #1143
Comments
Thanks for reporting, looking at your workflow: runs-on:
- self-hosted
- linux
- ARM64
container:
image: ghcr.io/leocencetti/docker:latest
options: --privileged
credentials:
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
volumes:
- /var/lib/docker:/var/lib/docker
- /var/cache/github-runner:/tmp/cache/ This does not look like a common setup 😅 What is the Also not sure what kind of runner you're using looking at |
This is roughly equivalent to this dockerfile, I am just using
Yes, I am using a docker-in-docker (DIND) workflow on a self-hosted ARM64 runner (NVIDIA).
Yes. I've collected the logs from relevant jobs in the workflow. I have omitted the docker build logs as they contain private info (and are probably unrelated). On a side note, the image I am building is on the larger side (some GB), and the full workflow logs are quite verbose (5k+ lines). I noticed that the logs are fetched by the action to produce the summary, so I am wondering if their size could be the issue. I don't seem to have this problem when building smaller (and less verbose) images using the same setup. |
Thanks! Looking at the logs it seems you're using an old version of buildx:
That doesn't support Can you make this change in your workflow to use latest stable and see if it fixes the issue on your side?: - name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
version: latest
buildkitd-flags: --debug I will try to repro on my side with older version. Edit: Was able to repro: |
Opened #1145 to mitigate the issue. You can test with: - name: Build and push image
uses: crazy-max/docker-build-push-action@summary-check |
@crazy-max I tried this morning to run the CI workflow with the latest docker buildx --builder builder-3e2fdd69-2ba2-4478-b367-2501d8cef169 dial-stdio
docker run --rm -i -v /github/home/.docker/buildx/refs:/buildx-refs -v /__w/_temp/docker-actions-toolkit-0j650g/export:/out docker.io/dockereng/export-build:latest --ref-state-dir=/buildx-refs --node=builder-3e2fdd69-2ba2-4478-b367-2501d8cef169/builder-3e2fdd69-2ba2-4478-b367-2501d8cef1690 --ref=b5ap7n4x5arkdbv617hvgbprg --uid=0 --gid=0
2024/06/20 06:42:45 failed to fill local state: failed to stat local ref directory /buildx-refs/builder-3e2fdd69-2ba2-4478-b367-2501d8cef169/builder-3e2fdd69-2ba2-4478-b367-2501d8cef1690: stat /buildx-refs/builder-3e2fdd69-2ba2-4478-b367-2501d8cef169/builder-3e2fdd69-2ba2-4478-b367-2501d8cef1690/: no such file or directory
Warning: Failed to export build record: /__w/_temp/docker-actions-toolkit-0j650g/export/rec.dockerbuild not found Note, I am not using your latest fix yet, although I doubt it will help here ( Full logs: |
Temp folder Can you add these extra steps after - name: Check docker config
run: |
tree -punahig /github/home/.docker
- name: Dump context
uses: crazy-max/ghaction-dump-context@v2 |
Hi crazy-max, I'm getting the same error as leocencetti. We're using our own GitHub runner and the docker/bake-action@v5.6.1 - I can provide the logs from the extra two commands above from our system. As this issue is closed, would here the best place for them or would an issue in the bake-action repo be more appropriate? Thanks! |
Contributing guidelines
I've found a bug, and:
Description
The generation of the build summary in the post-build job (added by https://github.com/docker/build-push-action/releases/tag/v6.0.0) fails
Expected behaviour
Generation should succeed
Actual behaviour
The post-build job fails unexpectedly with the following error:
error: Unavailable: connection error: desc = "error reading server preface: http2: frame too large"
The error can be reproduced when rerunning the workflow
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
BuildKit logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: