Bouke van der Bijl

This might actually be surprisingly easy, for cloud hypervisor the interface is that you create a unix socket on the host and then that gets bound to a vsock on...

I tried to do this, but unfortunately cloud-hypervisor doesn't support datagram vsock: https://github.com/cloud-hypervisor/cloud-hypervisor/issues/6307 which is what systemd uses for notifications

Figured it out, systemd can actually use a `vsock-stream:` notification socket, see: https://github.com/astro/microvm.nix/pull/219

A future version of systemd will make it easy to connect to a running VM over VSOCK: https://github.com/systemd/systemd/pull/30777 which this project can use!

My understanding is that the stack trace should be appended to the error message with two newlines between them. This might have to be done with a custom `Encoder`

Oh right: I want to run a reverse proxy (nginx) in front of its API, and I'd prefer not to run the risk of exposing it over the network.

I got it here: https://github.com/NixOS/nixpkgs/pull/89553 which is a vim plugin PR that I adapted to work. It's a bit weird because it calls a generated nix file inline, which I...

Right, that's what I figured. Thanks for the clarification 🙂. Would be very helpful if the error message was 'Import from derivation is not allowed' or something for a noob...

Yes, but that doesn't help with IFD unfortunately because it needs to evaluate the derivation on the host side before starting the build

Same as this one probably: https://github.com/cdcseacave/openMVS/issues/1107