Comments (7)
@felipecrs, if i'm understanding K3OS approach correctly, K3OS is only capable of launching containers through K3s. If that's the case, then, before we deal with this issue, we must first allow K3s to launch Sysbox PODs, which is something we don't quite support yet. So sounds like we may need to postpone this one till Sysbox PODs feature is implemented.
Let me know if i'm missing something here (K3OS is new to me).
from sysbox.
Please tell me if any of the following points are wrong:
- sysbox only supports docker, not containerd
- there is how to use docker instead of containerd in k3s: https://rancher.com/docs/k3s/latest/en/advanced/#using-docker-as-the-container-runtime
- after setting up k3s to use docker instead of containerd, we would only need to setup docker to use sysbox as the runtime
- k3OS: how to install Docker and make underlying k3s use it instead? (not a sysbox problem, I'll probably open an issue there)
- k3OS: how to install sysbox? Is it possible?
from sysbox.
I'm sorry about this, I'm now a bit confused about the technologies.
But what prevents pods to be spawned using sysbox?
from sysbox.
Not a problem at all Felipe, too many technologies and acronyms to keep track of in this space ;-) Please see below ...
-
Sysbox is a low-level runtime, so it executes at the same level of runc. Sysbox interacts with higher-level runtimes such as containerd (over which docker relies). Fyi, our goal is to have Sysbox talking to all OCI-compliant high-level runtimes (i.e. podman, crio, etc).
-
K8s/K3s can rely on 1) docker+containerd OR 2) just containerd (there are other approaches, but let's stick to these two for now). And you are suggesting to make use of 1) coz Sysbox is already able to handle docker containers. But it's not that simple, coz in K8s case we are dealing with PODs, not just individual containers.
The issue with PODs is that there are shared kernel namespaces among the various 'containers' that form a POD, and there is a tricky situation that we need to handle when dealing with unprivileged user-namespaces and shared network-namespaces. I'll create an issue for this one soon so that you can read through all the details if you're curious about it.
- Concerning this: "k3OS: how to install sysbox? Is it possible?" Mmm, there's no apt-get and no dpkg, so system is expected to be inmutable ... no installation possible other than through Helm channels. Can't think about any trivial approach to fix this, would need to think deeper about it.
Hope this makes sense, let me know otherwise.
from sysbox.
@felipecrs, this is the issue i talked to you about: #67.
from sysbox.
Makes super sense, thank you so much for the explanations.
Regarding PODs, maybe my own situation can be a bit different since I want to use sysbox
to spawn Docker in Docker Jenkins build agents (with my image jenkins-agent-dind), using the Kubernetes plugin for Jenkins. In that case, each pod will have a single container, which will be the build agent.
In any case, I subscribed to #64.
from sysbox.
Just as a heads-up: I'm not waiting for this feature, and I'm not a potential user of it as well.
from sysbox.
Related Issues (20)
- podman/buildah cannot list nestybox+cri-o containers HOT 2
- AKS sysbox nodes sporadically enter bad state (`stat failed on /var/lib/containers/storage/overlay/...`) HOT 16
- docker: Error response from daemon: unknown or invalid runtime name: sysbox-runc. HOT 1
- AKS sysbox container missing /proc/sys/net/ipv4/neigh/default HOT 8
- No such file or directory - unprivileged_userns_clone HOT 8
- Sysbox doesn't work with estargz compressed images
- Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? HOT 6
- EKS 1.28 won't install sysbox through sysbox-deploy-k8s daemonset HOT 5
- Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? HOT 3
- content of /proc/sys/kernel/random/uuid is always the same HOT 2
- Error in supervisord.conf of jenkins exemplary docker file HOT 2
- Kubernetes 1.29 support HOT 1
- failed to create sysbox-mgr: ID-mapping check failed on ZFS HOT 3
- can't build sysbox-in-docker image. `sysbox-runc` binary not available HOT 2
- writing /etc/resolv.conf caused: open /etc/resolv.conf: permission denied: unknown without "userns-remap":"sysbox"; kernel version is fine HOT 4
- sysbox k8s directory mounted as nobody HOT 9
- ingress networking in docker swarm in dind not working.. it's working fine on the docker host HOT 1
- Docker Desktop Compatibility (Windows 11) HOT 2
- Missing packages cmp, slices with 4a266da HOT 2
- sysbox-fs high cpu usage, infinite unmount calls on shared device HOT 11
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sysbox.