[pkg-go] Bug#1070727: reportbug: podman does not run wasm/wasi images because of missing crun-wasm - easy fix
Thanks for looking into this, On Sat, May 11, 2024 at 6:00 AM Faidon Liambotis wrote: > 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? > I think we should do either 1 or 2 to minimize divergence with upstream. My preference would be 2 to enable an out-of-the box experience. Is there any reason to not have that symlink installed by default in the `crun` package? -- regards, Reinhard ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#1070727: reportbug: podman does not run wasm/wasi images because of missing crun-wasm - easy fix
Hi, I tried to configure podman to use crun-wasm and failed. There seems to be 11 references in the org https://github.com/search?q=org%3Acontainers%20crun-wasm=code . So the safer option would be to package crun-wasm IMO. Asked for more information in the issue https://github.com/containers/crun/issues/1468 . I would add the symlink. Other programs might look for the binary. Looking at the references to crun-wasm I think having a crun-wasm package that: - depends on crun and wasmedge - creates a symlink to crun does not sond so bad. On the other hand, maintaining an extra package does not sound that nice either. Regards, Eugen La 11.05.2024 12:55, Faidon Liambotis a scris: 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 -- Eugen Stan +40770 941 271 / https://www.netdava.com ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Processed: Re: Bug#1070727: reportbug: podman does not run wasm/wasi images because of missing crun-wasm - easy fix
Processing control commands: > tags -1 confirmed Bug #1070727 [podman] reportbug: podman does not run wasm/wasi images because of missing crun-wasm - easy fix Added tag(s) confirmed. -- 1070727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#1070727: reportbug: podman does not run wasm/wasi images because of missing crun-wasm - easy fix
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 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
