Skip to content
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

[Bug]: Build and push image ERROR: failed to solve: error writing layer blob: #506

Open
ll7 opened this issue Nov 15, 2024 · 2 comments
Open
Labels
bug Something isn't working infrastructure Docker, Project setup, ...

Comments

@ll7
Copy link
Member

ll7 commented Nov 15, 2024

Current Behavior

Build and push image

during step Test build

https://github.com/una-auxme/paf/actions/runs/11833373479/job/32971904647?pr=505

#41 ERROR: error writing layer blob: mkdir /tmp/.buildx-cache/cache-new/test/ingest/5c89f3f2bc1419604464985c6cbfb0c25e197dc9cd3cc640cb4cd901f1a5f7a7: no such file or directory: unknown
------
 > exporting cache to client directory:
------
ERROR: failed to solve: error writing layer blob: mkdir /tmp/.buildx-cache/cache-new/test/ingest/5c89f3f2bc1419604464985c6cbfb0c25e197dc9cd3cc640cb4cd901f1a5f7a7: no such file or directory: unknown
Error: buildx failed with: ERROR: failed to solve: error writing layer blob: mkdir /tmp/.buildx-cache/cache-new/test/ingest/5c89f3f2bc1419604[464](https://github.com/una-auxme/paf/actions/runs/11833373479/job/32971904647?pr=505#step:6:468)985c6cbfb0c25e197dc9cd3cc640cb4cd901f1a5f7a7: no such file or directory: unknown

Expected Behavior

No error during Test Build

Steps to Reproduce

Unknown

Definition of Done

Error fixed

Effort Estimate

No response

Testability

Unknown

Dependencies

No response

@ll7 ll7 added bug Something isn't working infrastructure Docker, Project setup, ... labels Nov 15, 2024
@ll7
Copy link
Member Author

ll7 commented Nov 19, 2024

@JulianTrommer
Copy link
Member

This issue is due to the setup of multiple runners since each one is reading from and writing to the same location.
If two runner run simultaneously one of them will delete the cache that the other runner wants to read.
We will circumvent this issue by removing all but one build runners (since the build action with caching only takes ~6mins).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working infrastructure Docker, Project setup, ...
Projects
Status: No status
Development

No branches or pull requests

2 participants