crun

crun copied to clipboard

crun +WASM:wasmer can't run wasix modules

2

``` fn main() { println!("Hello, world!"); } ``` if I build the above Rust code as a wasm module with `cargo build --target wasm32-wasi --release` its image is successfully executed...

JohnFrrr

Supporting additional WASM runtime

5

Hi, I'm new here but exploring using crun on baremetal linux embedded system. Going through the build files I figure WASM is supported experimentally and few WASM runtime options are...

hardiksd

If libkrun-sev is installed, but /dev/sev doesn't exist, rootless krun fails

3

If libkrun-sev is installed, but there is no `/dev/sev`, rootless krun will attempt to bind mount a `/dev/sev` that doesn't exist into containers, even for containers which aren't using SEV....

nalind

Failure in changing the docker restart policy

1

crun works great with docker when trying to bring the containers up. However, when we try to run something like this command on a running container: docker update --restart always...

Lorsh

I've been looking for ways to ascertain the high-water-mark memory usage for a running container, and one suggestion given was `runc events --stats `. `crun` doesn't currently seem to implement...

srcshelton

Exposing/leveraging filesystem features for containers (casefolding, reflinks)

14

In a discussion during [Container Plumbing Days](https://containerplumbing.org/) 2023, @rhatdan and I got to talking about running Windows applications as Linux containers using Wine. He mentioned that there are filesystem quirks...

Conan-Kudo

OCI runtime error: crun: mount `proc` to `/proc`: Too many levels of symbolic links

12

(Continuation of discussion from https://github.com/containers/crun/issues/1115 ) yes, that seems like a different error and one I've never seen before. Do you see the same error if you run something like...

satmandu

Packit: issues with configure args

1

Looks like the %{wasmedge_opts} and other configure args aren't correctly being read by rpm builds. I'd like to get this fixed before the next upstream release.

lsm5

crun should never checkpoint the netns

12

Basically the same as 2a0947e601c354f0c63a3802f8084db1b23e1851 but this made the exception to checkpoint the netns when the netns path is empty in the runtime spec. This works only for the case...

Luap99

read from the init process error

13

try run: ```sh /usr/bin/crun --cgroup-manager=cgroupfs --root=/vm/root run --pid-file=/vm/run/test.pid --preserve-fds=3 test ``` work for 1.7.2, after 1.8.0, there is a error https://github.com/containers/crun/pull/1201 just fixed few day ago. with 1.8.4, and patch...

calvin2021y