-
Notifications
You must be signed in to change notification settings - Fork 549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Non runc runtimes #3922
Comments
This would be a great feature. I use sysbox for both professional and personal use and I would love to see this in Talos! |
Would this also include support for runtime like I already run crun with wasm enabled on some onprem clusters. I'm really interested in talos. Can I just add the needed binaries and configure containerd oder is this not supposed yet? |
Containerd is the only runtime supported, but wasm,gvisor etc are supported via extensions: https://github.com/siderolabs/extensions |
We also have some deployment using sysbox as a runtime ( gitlab runner, coder.com, and other « untrusted » code ) We didn’t find any workaround, so we cannot use talos right now It will be great to have these implemented |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Feature Request
support for other runtimes (like sysbox). This would allow us to run container virtualization workloads on Talos.
Description
We've successfully deployed Talos inside of our Proxmox hosts and are happily deploying applications, but one of them has the ability to utilize CVM (container virtualization) using sysbox. it looks like the resources it requires are more than Talos exposes - is this even possible with Talos, or will I need to create some bespoke workers for this application?
From the application docs:
CVMs leverage the Sysbox container runtime, so the Kubernetes Node must run a supported Linux distro with the minimum kernel version (see Sysbox distro compatibility for more information)
The cluster must allow privileged containers and hostPath mounts. Read more about why this is still secure here.
The text was updated successfully, but these errors were encountered: