Closed danbugs closed 2 years ago
Hey, @KaiWalter ~ Thank you for your question. I definitely should gone back and included descriptions to issues like this once we open sourced.
That said, this issue will most likely be a contribution to:
Are you familiar with Fermyon's Spin? If you check the containerd-wasm-shims repo, you'll see we've got a shim for it that helps serve a containerized Spin app. We hope to do something similar for Slight. I hope this clarifies the scope of the issue — let me know if it doesn't!
Hi @danbugs, I see. That was actually, what I was talking about with @squillace 2 weeks ago: "get WASM/WASI workloads running in cluster or other environments without using OCI containers". For the moment I have to admit, that the repos you listed above are technically somewhat out of my league. So don't wait for me, please. Anyway as I want to use my vacation time for building up some Rust muscle I will definitely munch into those.
@danbugs - After I figured out how runwasi is working, I can imagine to get slight
and a module WebAssembly packaged up with a containerd-shim approach. But still using docker buildx
to build the image.
@squillace - But then why? Why go to all the length to patch WebAssembly execution into containerd ecosystem? Just to then make it easier to hook it up with K8S based hosting? Wouldn't just aiming for a clustered process orchestrator like Service Fabric be the simpler approach here?
I did some preliminary tests and the only shortfall I currently see is, that SF up till now only supports Ubuntu up to 20.04 which makes patching some of the slight dependencies into the nodes somewhat hard. If we could get support for 22.04 nodes, that should be far more easier.
Hi @KaiWalter was out for a few days to repower. I have only partially repowered. :-| But YES, the objective will be to have a containerd-based integration into k8s. There are several reasons.
docker run --runtime=io.containerd.wasmtime.v1
now and more direct work will arrive. Nonetheless, I also expect that standalone hosts like slight or spin or wasmcloud (which is its own orchestrator I note) will be popular in all areas in which k3s makes no sense as a control plane. As they should be.
@squillace thanks for the explanation - got it. This is fascinating stuff. You know I've not been doing kind of "systems programming" since early 90ies. This really strikes a chord. I will be off the grid for a few days - also unwinding a bit. I'd really like to contribute. Do you perhaps run a more tactical forum like Discord, Gitter, ...? Also Teams/microsoft.com tenant would work for me.
Wait, @KaiWalter, you're on vacation but you want "tactical"? :-P
For work with slight, just post issues! everyone can see and learn, which is an advantage. For more focused issues, mail me at ralph.squillace@
@squillace I need this to unwind - https://twitter.com/ancientitguy/status/1560892996991782913 - with all those heavy duty enterprise projects I usually do, where technological challenges are easily trivialized by the complexities on organization, process or social level.
~check out slight (previously, wasi-cloud
) running on a PinePhone:
video link: https://user-images.githubusercontent.com/39843321/186492047-68cf490b-1629-4113-a6dc-bb8f01bc8304.mp4
P.S. might have to click on it to zoom in or view video
Closed this issue as we move containerd related issues to https://github.com/deislabs/containerd-wasm-shims
@danbugs what exactly would you like to achieve with this issue? Is it just containerizing one
slight
workload like in https://github.com/KaiWalter/spiderlightning/blob/hosting-service-fabric/cluster/cluster-test/Dockerfile)?