Live data from Hacker News

MicroVMs: Run isolated sandboxes with full lifecycle control

aws.amazon.com

221–222 of 222 posts

Re: MicroVMs: Run isolated sandboxes with full lifecycle control

#221
post #92
post #69

Earlier quoted context omitted.

You can't run firecracker on AWS.

You can with the newer instances that suport nested VM. There was a recent story about this here https://news.ycombinator.com/item?id=48556561 .

I meant to say on Hetzner...

Re: MicroVMs: Run isolated sandboxes with full lifecycle control

#222
post #218

Earlier quoted context omitted.

There is something wrong with your setup. I just tried: bwrap ... --ro-bind /run/user/1000/pipewire-0 /run/user/1000/pipewire-0 ... -- runsc ... do ... -- mpv podcast.mp3 Flawless playback. I think it's a default pipewire configuration.

Ah, I see the distinction. In my case, I was using the PulseAudio client+server with a network sink running in-sandbox, producing a set of audio samples that are then replayed by a PulseAudio client in the out-of-sandbox Rust application receiving these samples. Exposing the socket directly to the sandbox is dangerous, e.g. it would let the sandbox record the host's microphone directly. My goal was for the sandbox to…

> Exposing the socket directly to the sandbox is dangerous, e.g. it would let the sandbox record the host's microphone directly.

libpipewire-module-pipe-tunnel

also: https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_req...>

Post reply on HN