Closed joh-klein closed 4 months ago
Does retrying the run with debug logs enabled show anything useful?
Nope. Could find anything. Also adding buildkitd-flags: --debug
to the Setup-Action didn't show anything different
I will temporarily go back to the original gha cache to see, if it has anything to do with the kubernetes driver and setup (the cache worked before in k8s but I didn't switch to the k8s driver then). It would be super cool if there was a way to switch to the original cache without rebuilding the runner image …
The "OG" cache doesn't have the problem:
#15 exporting to GitHub Actions Cache
#15 preparing build cache for export
#15 writing layer sha256:32d9857c4f4835a493d21463dcc7e498a59bdb44ac621f2ffa10f2bf825246c5
#15 writing layer sha256:32d9857c4f4835a493d21463dcc7e498a59bdb44ac621f2ffa10f2bf825246c5 2.3s done
#15 writing layer sha256:7c65fb70bae1fc6a6df9187fb36d80d39ffa9e4a89597418d78a086004a83ed7
#15 writing layer sha256:7c65fb70bae1fc6a6df9187fb36d80d39ffa9e4a89597418d78a086004a83ed7 0.3s done
#15 writing layer sha256:c21ce77c4b0c7b34e732f4d19fa0c5b00dda745586f3946cbbc64666ddaab3f3
#15 writing layer sha256:c21ce77c4b0c7b34e732f4d19fa0c5b00dda745586f3946cbbc64666ddaab3f3 0.3s done
#15 writing layer sha256:f0513f0e14e7c79ed978751b5310e20be390ed51ce00163514198b291ef8d200
#15 writing layer sha256:f0513f0e14e7c79ed978751b5310e20be390ed51ce00163514198b291ef8d200 0.3s done
#15 preparing build cache for export 5.1s done
#15 DONE 5.1s
Is there more log output from your side I can activate? Maybe the cache server doesn't accept the blobs correctly …
I'll look into it
Thank you for fixing it so quickly!
Worfklow setup (after I got it to work in #41):
At the start of the step, I can see this in the logs from the cache server:
At the end of the docker build step, the cache upload fails with:
I don't know (yet) how to get more meaningful output