You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Buildx is only using a cache of one architecture, due to which our building images are taking so much time to build multi-arch images. This is due to using the --cache-to=local option and pushing the cache to s3 for both AMD and ARM arch in the same location. We need to enhance the cache behaviour for buildx to push both AMD and ARM arch caches.
🎤 Pitch / Usecases
For this problem statement to solve we can use --cache-to=registry or --cache-to=local but with different names for AMD and ARM.
🔖 Feature description
Buildx is only using a cache of one architecture, due to which our building images are taking so much time to build multi-arch images. This is due to using the --cache-to=local option and pushing the cache to s3 for both AMD and ARM arch in the same location. We need to enhance the cache behaviour for buildx to push both AMD and ARM arch caches.
🎤 Pitch / Usecases
For this problem statement to solve we can use --cache-to=registry or --cache-to=local but with different names for AMD and ARM.
Can follow this GH discussion for more info docker/buildx#1382 and issue: docker/buildx#1044
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
Subtasks
QA Subtasks
AB#9340
The text was updated successfully, but these errors were encountered: