Kevin Flansburg

I believe that Krustlet uses the client in the OCI Registry crate (https://github.com/deislabs/krustlet/tree/main/crates/oci-distribution) to pull wasm images. What is the Pod manifest that you are trying to run? Does Krustlet...

Once the following merge I will publish a new crate version for Krator: - https://github.com/krator-rs/krator/pull/64 - https://github.com/krator-rs/krator/pull/65

@flavio `krator` v0.6.0 is published with the new version of `tokio`.

I believe that the advisories are a known issue, but the windows tests are probably caused by the same `native-tls` feature that they were on `krator`.

> I've just tried to build with the latest changes I submitted on a windows box. Everything builds fine. > > However, the really old tokio 0.2 crate is used...

@bacongobbler @thomastaylor312 The rerun of Windows e2e failed. It looks like Docker never becomes ready. I'm not familiar with how this runner is configured or who hosts it.

I agree that implementing this logic in Kubelet doesn’t make much sense. Perhaps this could be a Provider instead which manages other homogeneous providers so that we do not have...

I cannot recall where, but I believe I read somewhere that the Kubernetes spec for a Pod explicitly disallows something like this. So we are fighting the API a bit...

Well the pod makes requests for a given architecture. So they must both agree. It may have been Nodes that I read the limitation about though. > On Jun 24,...

I think my plan was to modify the pod definition to create two pod definitions containing only containers from each architecture and then forward them to the respective providers. I...