fermyon
Not able to pull Wasm module from OCI registries, in 2.7.0, which I was able to pull in 2.6.0
The following error message is being shown when running spin up
3: registry error: Wasm components must have a config of type application/vnd.wasm.config.v0+json
4: Wasm components must have a config of type application/vnd.wasm.config.v0+json
Tracked this down with @radu-matei to be changes in this PR: https://github.com/fermyon/spin/commit/b766cc4d162c987054d19689f68aa3952e9bcae6, and thus associated changes in wasm-pkg-loader - probably this: https://github.com/bytecodealliance/wasm-pkg-tools/commit/4c08fb278d6f0d8599d9f6d1c139f9fd88daeb8c - but now we are speculating!!!
@itowlson I think you've encountered similar issue?
The older code predated https://tag-runtime.cncf.io/wgs/wasm/deliverables/wasm-oci-artifact/
@mikkelhegn I was able to publish with wkg oci (and I think now there is a wkg publish) and I believe that is compatible with the version of wasm-pkg-loader that Spin 2.7 uses.
There was an older convention that used a lengthy oras incantation to publish - unfortunately I don't think wasm-pkg-loader still supports that older format. I can try to do come compatibility shenanigans if necessary but this remains an experimental feature and I would prefer not to have to...!
Put another way, we (I) jumped the gun on including registry components before the spec was stable - I totally put my hands up to that.
Given that we haven't heard other reports of this breaking change we're going to close this as stale. Feel free to re-open if there are ongoing issues to resolve.