4 ms·
maintainer, I would recommend trying out: https://github.com/smol-machines/smolvm https://github.com/smol-machines/smolvm It has network filtering + placeholde
by binsquare 2mo ago
maintainer, I would recommend trying out: https://github.com/smol-machines/smolvm https://github.com/smol-machines/smolvm
It has network filtering + placeholders for secrets.
OSS, no logins needed
- reddec 2mo agoI've put some effort to integrate it to my agentic workflow. The problem, however, with docker in smolvm: it work-ish (there is example), but quite hacky. Another problem which I wasnt able to solve - persistent image without Dockerfile. CloudInit will be ideal. Documention at this moment in an early stage. Overall, its a great project but for me was simpler just use Virtual Machine Manager (libvirt GUI). I wish all luck to the maintainers, but probably DX-wise I will prefer to have more granular or predictable controls (eg micro cloud from Canonical).
- icedchai 2mo agoThere's also microsandbox which has similar features: https://github.com/superradcompany/microsandbox https://github.com/superradcompany/microsandbox (Not affiliated with them, just tried it out last week.)
- binsquare 2mo agoI'm aware of them! Yep - similar in some ways but headed towards different directions. I am building a virtual machine to simplify/replace container infra. Ex. we run containers inside of linux VM's even in the `cloud`, resulting in managing both the vm, and the containers. But smol machines is a lightweight, portable VM that you can package into a single portable .smolmachine file to be rehydrated on any platform, kind of like how containers are used for today. Sandboxing happens to be a feature of virtual machines, so we are alike in being used for sandboxing.