#@Erik Sipsma have any idea why I'm
mossy sparrow
getting it locally too, my best guess is that because we are using the :latest tag on the image we pull we hit a backwards incompatible change? I'll see if changing locally to use a different tag for an older release fixes, not actually important for the test case to use latest
Oh, I guess they only give you latest unless you pay them for enterprise support (fair): https://edu.chainguard.dev/chainguard/chainguard-images/reference/apko/tags_history/
odd blade
So we need the digest 🙂
mossy sparrow
I'll check what other quick fixes there are; we also don't really have to use apko there but it's nice to verify against something external rather than just verifying we can load container images we also produced but that would be a fallback
mossy sparrow
So we need the digest 🙂
Yeah unless of course they prevent you from even doing that without having enterprise support 🙂
they just don't support that flag anymore: https://github.com/chainguard-dev/apko/pull/942
But we do want coverage that we can load tarballs that use docker media types... I'll try updating the test to just use something besides apko