fix: 馃悰 build fail Failed to Load Docker Image Metadata #36
Conversation
| @@ -25,6 +25,8 @@ runs: | |||
| steps: | |||
| - name: Set up Docker buildx | |||
| uses: docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb # v3.3.0 | |||
| with: | |||
| use: 'false' | |||
There was a problem hiding this comment.
@EduarteXD I see this:
.. but I don't know enough about how Docker or buildx works to know what "Switch to this builder instance" means or what effect it might have.
There was a problem hiding this comment.
In buildx, the --use parameter is used to specify an existing builder.
In the setup-buildx-action script, passing use: true will make each build step use a new builder instance, each builder has its own context, cache, and storage space.
Therefore, the artifacts (such as intermediate layer cache, final images, etc.) between different builders are isolated by default and cannot directly access each other鈥檚 artifacts.
In each step of the cog's build, it is necessary to use --load to directly load the built image into the Docker engine, which can take a considerable amount of time.
There was a problem hiding this comment.
Gotcha! Thanks for explaining in detail. I can set up a test workflow that combines this change plus replicate/cog#1656 and see how it goes. If everything is smooth I'll merge and ship these changes.
Please see replicate/cog#1656