flouthoc

@matthias50 Yes both `1.21.6` and `1.20.6` are using significantly older version of `c/storage` if you could try a small experiment suggested here https://github.com/cri-o/cri-o/issues/5793#issuecomment-1098775717 it will confirm my hypothesis. > @matthias50...

@matthias50 Sorry I was not clear enough :\ but my intention was to not invoke `crictl pull` at all but only invoke `podman pull`. But still thanks for trying this...

I am actually able to reproduce this but by manually adding failures i.e skipping certain parent layers by instrumenting code here https://github.com/containers/storage/blob/main/drivers/overlay/overlay.go#L911 ```go func (d *Driver) create(id, parent string, opts...

@haircommander @matthias50 I was unable to reproduce this when i tried this last-time without manual instrumentation of code but sure let me try again and see if I can reproduce...

@twojenski Would it be possible to share a small reproducer or environment details. I pulled exact same podman and tried reproducing on `vfs` storage but I'm not able to reproduce,...

@matthias50 Is it similar to your case, does the stuck image gets resolved if you create missing directory manually ?

> @flouthoc, I see from this comment that you are using `vfs` for the replication attempts: @matthias50 I only used `vfs` just to reproduce scenario shared here https://github.com/cri-o/cri-o/issues/5793#issuecomment-1207440047 by @terinjokes...

Hi Team, If I read the issue correctly I am working on similar feature for `crun` (OCI-runtime) which already supports `wasmedge` and `wasmer` and following PR adds supports for `wasmtime`...

Hi @dave-tucker , Thanks for creating the issue. Could you please share `podman info` as well. Does it works fine for your if you run a regular container e.g `podman...

I defiantly see an issue with args being propagated to wasmtime invocation but there are few question above could you please answer those. I'll try to submit a patch for...