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
But why are you not using one of the default arch/distro if those are the images you want to use? A workaround for the cache issue is creating your own new dockerfile in Dockerfiles, cloning one of the existing ones.
I'm not using arch and dist because they just don't work, except for buster. But now, should I use arm/v7 as arch instead of filling base_image as in my 1st message ?
When starting the action, Docker fails with
no match for platform in manifest: not found
whereas buster still works ok.Trying the new syntax forcing the platform works for aarch64 but fails on armv7 for bookworm and bullseye. In other words:
--platform=linux/armv7 arm32v7/debian:buster
--platform=linux/armv7 arm32v7/debian:bullseye
--platform=linux/armv7 arm32v7/debian:bookworm
--platform=linux/aarch64 arm64v8/debian:buster
--platform=linux/aarch64 arm64v8/debian:bullseye
--platform=linux/aarch64 arm64v8/debian:bookworm
On a side note, not specifying arch and distro makes packages cache useless since all these "none-none" overlap eachother.
The text was updated successfully, but these errors were encountered: