[pkg-go] Bug#1070727: reportbug: podman does not run wasm/wasi images because of missing crun-wasm - easy fix

[Faidon Liambotis]

Control: tags -1 confirmed

On Wed, May 08, 2024 at 03:10:40AM +0300, Eugen Stan wrote:
> I followed the guide to run wasm images on my system and it failed with
> errors.
> 
> I believe the issue is that podman looks for crun-wasm binary by default.
> I failed to configure podman to use crun instead of crun-wasm.
> I created a simbolic link named crun-wasm:
> 
> sudo ln -s /usr/bin/crun /usr/local/bin/crun-wasm

Ouch! You're right. This worked when I enabled WasmEdge in crun, but
was changed upstream at some point since.

Apparently Fedora/RedHat ship a "crun-wasm" package, which contains a) this
symlink, b) a dependency on WasmEdge.

In Debian, the main "crun" package has a Suggests on libwasmedge0.

I see three paths forward:
1) We do the same, creating a new (almost) empty package.
2) We ship a /usr/bin/crun-wasm symlink in the crun package.
3) We patch podman to use /usr/bin/crun instead of, or in addition to,
/usr/bin/crun-wasm.

I don't particularly love option (1). I'm split between options (2) and
(3), not loving either.

Thoughts?

Faidon