Docker: fix relative paths, required after upgrade to bake-action@v6#6835
Docker: fix relative paths, required after upgrade to bake-action@v6#6835khsrali wants to merge 1 commit into
bake-action@v6#6835Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6835 +/- ##
=======================================
Coverage 78.29% 78.29%
=======================================
Files 566 566
Lines 42764 42764
=======================================
Hits 33479 33479
Misses 9285 9285 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull Request Overview
This PR updates the Docker workflow configuration to fix relative paths after upgrading to bake-action v6. Key changes include switching from using "workdir: .docker/" to "source: ." and updating file paths for docker build files from "docker-bake.hcl" and "build.json" to ".docker/docker-bake.hcl" and ".docker/build.json".
Files not reviewed (1)
- .docker/docker-bake.hcl: Language not supported
|
Thanks. The problem was sourced from https://github.com/docker/bake-action/releases/tag/v6.0.0 where the action start to use git_context. @khsrali could you give it a try? If using path context, with the change you did, I guess it will break the local build flow as documented in the readme https://github.com/aiidateam/aiida-core/tree/main/.docker#aiida-docker-stacks. Those commands are supposed to run from inside the |
Good point, wasn't aware of that |
564526b to
663ea79
Compare
|
not working. |
|
No time to dig into this. |
Solving stupid backward non-compatible errors of docker after upgrade.