News for hackers. Stuff that matters.
Re:Devvm.dev: One VM for every project by mnahkies on Friday November 06, 2026 @03:26PM (#50397983)
One thing I'm struggling with at the moment which I may as well ask here.

Many of my projects use pnpm, which ideally uses hard links from a shared store of dependencies.

One of my goals is to reduce the disk overhead of VM based isolation, so I'd like a shared pnpm store across projects (and the same for maven, etc as well)

With https://virtio-fs.gitlab.io/ mounts, each mount inside the VM is a separate FS, and I can't hard link across them. I've tried playing around with ideas like bind mounting the directory structure from the host in a folder to have a single virtio-fs mount inside the VM - but the bind mounts still can't be hard linked across it seems.

I'm basically wondering if I'm missing something or just trying to do something that isn't possible.

All the host folders are on the same FS - but I don't want to organise the host system around the VM mounting needs, and I also don't want to mount extraneous directories into the VM (eg: simple solution could be just mount ~/projects but kinda self defeating)

(Fedora workstation host)

Re:Devvm.dev: One VM for every project by genxy on Friday November 06, 2026 @05:52PM (#50399586)
Use a host fs that supports CoW.
Re:Devvm.dev: One VM for every project by j4k0bfr on Friday November 06, 2026 @09:46PM (#50401135)
I agree with the sibling here, copy-on-write is probably the best option. And shared writable store between VMs is an absolute nightmare for stability and security. My experience with C/C++ shared build caches was miserable, lol