sysbox
sysbox copied to clipboard
nestybox
An open-source, next-generation "runc" that empowers rootless containers to run workloads such as Systemd, Docker, Kubernetes, just like VMs.
podman/buildah cannot list nestybox+cri-o containers, if I want to perform operations similar to 'podman commit/tag' on nestybox+cri-o containers, is there any way to do it? crio-status config: ``` [crio] root...
I am attempting to add sysbox-runc to a concourse ci worker. The concourse deployment is a tarball of binaries including but not limited to containerd, containerd-shim's, init, ctr, runc, and...
Full logs are available here: https://download.copr.fedorainfracloud.org/results/karellen/karellen-sysbox/fedora-38-x86_64/06680595-karellen-sysbox/builder-live.log.gz Do I need to depend on the system's `libseccomp[-devel]` now? ``` make[1]: Leaving directory '/builddir/build/BUILD/karellen-sysbox-0.6.2.30/sysbox/sysbox-ipc' make[1]: Entering directory '/builddir/build/BUILD/karellen-sysbox-0.6.2.30/sysbox/sysbox-runc' fatal: not a git repository...
To integrate sysbox with other tooling it would be nice to be able to have a custom CRI-O config. I'd like, for example, to integrate sysbox with the [Stargz Snapshotter](https://github.com/containerd/stargz-snapshotter/blob/main/docs/INSTALL.md#install-stargz-store-for-cri-opodman-with-systemd)...
The tests/kind/kind-custom-net.bats test fails in CI for an unknown reason. However, it does not fail when executed locally, therefore the failure is likely a CI setup issue. Skip this test...
I'm attempting to mount squashfs images inside a sysbox runtime'd Kubernetes pod as a dependency of our Bazel build system. ``` ➜ sudo mount img.sqfs /mnt/img -t squashfs -o loop...
It is no longer possible to limit the root filesize limit of a container with `--storage-opt` (and an attacker can exhaust the host's inode or size limit - which can...
Hi, I have a GKE cluster with control plane version `1.26.8-gke.200`. I created a node pool with the same k8s version and deployed the Sysbox installer `DaemonSet`. That seemed to...
The `docker stats`command seems fundamentally flawed on sysbox containers, not showing changes in either cpu and memory usage, always stays on 1 PID, also not catching the limit when running...
