Repository navigation
Token Container | linuxarm64 #366
Replies: 2 comments 1 reply
|
It's not your Pi, the The Woodpecker pipeline pushes Until it's republished, pin the previous one, which is multi-arch. In your then You can check with |
|
Fixed since 1.15.0, the token image has both amd64 and arm64 again, so |

It's not your Pi, the
latesttag of the token image is amd64-only right now. The docker warning in your screenshot says it too: "requested image's platform (linux/amd64) does not match".The Woodpecker pipeline pushes
latest/1.11.1from the amd64 job first, then a manifest job is supposed to replace them with a multi-arch index once arm64 is done. For 1.11.1 the arm64 image never got published (there's no1.11.1-arm64tag on ghcr), so the manifest step didn't run andlateststayed amd64-only. The other TypeType images are fine, they have both archs.Until it's republished, pin the previous one, which is multi-arch. In your
.env: