Ugh. This still isn't quite what I want. I can't stand Docker. It's so damn heavy.
All I want is something like the following:
- Sandboxed applications
- With an agent to control which ones run on a machine
- A GUI to easily observe and manage deployments
- Infra-as-code using a sensible file format (anything but YAML)
I imagine this working best with VM-based runtimes like .NET and WASM. The ability to control resources consumption isn't there yet, but I don't see why you couldn't have a runtime that gives fine-grained controls over sandboxing and resource consumption.
This idea came about from observing discourse on replacing conventional hypervisors with WASM/WASI.
Forget Docker. Forget OCI. Forget Kubernetes/SWARM. We just need a simple system for orchestrating apps that are already VMs.
I find Docker running a full Linux userspace a little bloated. Thankfully there are distroless base images(https://github.com/GoogleContainerTools/distroless). Haven't done service dev in a while, so I don't really have experience with this, but it looks promising.
Distroless is great for things that compile to static binaries, I use it for Rust apps. For anything that pulls in heavy dependencies, having a package manager is convenient (alpine, debian-slim).
All I want is something like the following:
- Sandboxed applications
- With an agent to control which ones run on a machine
- A GUI to easily observe and manage deployments
- Infra-as-code using a sensible file format (anything but YAML)
I imagine this working best with VM-based runtimes like .NET and WASM. The ability to control resources consumption isn't there yet, but I don't see why you couldn't have a runtime that gives fine-grained controls over sandboxing and resource consumption.
This idea came about from observing discourse on replacing conventional hypervisors with WASM/WASI.
Forget Docker. Forget OCI. Forget Kubernetes/SWARM. We just need a simple system for orchestrating apps that are already VMs.