91–100 of 162 posts
Any integration with existing orchestrators? Plans to support any or building your own?
But should be easy for anyone to build their own integration with existing as well like nomad.
Earlier quoted context omitted.
Really appreciate the suggestion! By "live migration", do you mean keeping the existing files and migrate them elsewhere with the vm? Thanks
I mean making any given VM stop on host A and appear on host B; e.g. standard Qemu/KVM: virsh migrate --live GuestName DestinationURL This is feasible when network storage is available and useful when a host needs to be drained for maintenance.
My team spent 4 months on our implementation of vm memory that let us do it and its still our biggest time suck. We also were able to make assumptions like RDMA that are not available.
All that to say — as someone not working on smolVMs — I am confident smolVMs and most other OSS sandbox implementations will get live migration via hypervisor upgrades in the next 12 months.
Until then there are enterprise-y providers like that have it and great OSS options that already solve this like cloud hypervisor.
Hello, I'm building a replacement for docker containers with a virtual machine with the ergonomics of containers + subsecond start times. I worked in AWS previously in the container space + with firecracker. I realized the container is an unnecessary layer that slowed things down + firecracker was a technology designed for AWS org structure + usecase. So I ended up building a hybrid taking the best of containers with…
Hello, I'm building a replacement for docker containers with a virtual machine with the ergonomics of containers + subsecond start times. I worked in AWS previously in the container space + with firecracker. I realized the container is an unnecessary layer that slowed things down + firecracker was a technology designed for AWS org structure + usecase. So I ended up building a hybrid taking the best of containers with…
How is this different than Kara Containers?
smolvm is a vm with some of the properties & ergonomics of containers - it's meant as a replacement for containers.
Hello, I'm building a replacement for docker containers with a virtual machine with the ergonomics of containers + subsecond start times. I worked in AWS previously in the container space + with firecracker. I realized the container is an unnecessary layer that slowed things down + firecracker was a technology designed for AWS org structure + usecase. So I ended up building a hybrid taking the best of containers with…
Hey this is super cool. I've been researching tech like this for my AI sandboxing solution, ended up with Lima+Incus: https://github.com/JanPokorny/locki My problem with microVMs was that they usually won't run docker / kubernetes, I work on apps that consist of whole kubernetes clusters and want the sandbox to contain all that. Does your solution support running k3s for example?
The feature that lets you create self-contained binaries seems like a potentially simpler way to package JVM apps than GraalVM Native. Probably a lot of other neat usecases for this, too smolvm pack create --image python:3.12-alpine -o ./python312 ./python312 run -- python3 --version # Python 3.12.x — isolated, no pyenv/venv/conda needed
yeah, it's analogous to Electron. Electron ships your web app bundled with a browser. Smol machines ship your software packaged with a linux vm. No need for dependency management or compatibility issues because it is baked in. I think this is how Codex or Claude Code should be shipped by default, to avoid any isolation issues tbh
I can't actually create and test a pack right now because of [1], but I love the idea of using this to distribute applications you might otherwise use a Docker image for.
Earlier quoted context omitted.
[flagged]
Hey 'software engineer', how much of the output of an LLM it's actually reproducible vs the one from a calculator or any programming language with the same input in different sessions?
Non-determinism is a problem that you can mitigate to some extent with a bit of effort, and is important if your AI is running without a human-in-the-loop step. If you're there prompting it though then it doesn't actually matter. If you don't get a good result just try again.