Security Note (01/21/22):
A vulnerability (CVE 2022-0185) was recently found in the Linux kernel, permitting a "User Namespace" escape (i.e., an unprivileged user inside a user-namespace may gain root access to the host). This vulnerability affects containers deployed with Sysbox as they always use the Linux user-namespace for extra isolation. To mitigate it, check if your kernel distro carries the fix. For Ubuntu, the fix has been released and requires a kernel update. Reach out to the Sysbox Slack channel for further questions.
- Features & Pricing
- Supported Distros
- Host Requirements
- Using Sysbox-EE
- Filing Issues
- About Nestybox
- Thank You
Sysbox-EE uses Sysbox at its core, but adds enterprise-level features such as:
Improved container isolation / security
Running more types of system-level workloads inside containers
Scalability (running more containers per host)
Significant performance and efficiency optimizations (for faster container deployment with reduced disk utilization)
Lifecycle (higher release cadence, critical bug fixes ASAP)
Nestybox professional support with a guaranteed SLA (rather than best effort on Sysbox)
Feature prioritization (Sysbox-EE feature requests are prioritized)
For these reasons, **we recommend that enterprises that wish to use Sysbox in their IT infrastructure use Sysbox-EE**.
Sysbox-EE is a drop-in replacement for Sysbox. It installs and it's used in the exact same way, but includes the enterprise level features described above. On a given host however, either Sysbox or Sysbox-EE must be installed, never both.
See the next sectionfor a comparison between Sysbox-EE and Sysbox (aka Sysbox Community Edition or Sysbox-CE).
Features & Pricing
Sysbox-EE is offered via a 30-day free trial and a paid subscription after that.
Features and pricing info are shown below.
(*) For pricing purposes, a "host" is a computer (bare-metal or virtual-machine) with up to 16 CPU cores (32 hyper threads). Per-core pricing at $5 per-core per-month is also available for hosts with < 8 cores. Licensing is per-year. Volume discounts available for 50+ per-host licenses or 350+ per-core licenses.
You can download Sysbox-EE for free and use it during the free trial period. Afterwards, we ask that you contact Nestybox for pricing and payment information.
If you have questions, you can reach us here.
Sysbox-EE relies on functionality available only in relatively recent Linux kernel releases.
See the distro compatibility doc for information about the supported Linux distributions and the required kernel releases.
We plan to add support for more distros in the near future.
The Sysbox-EE host must meet the following requirements:
It must be running one of the supported Linux distros.
We recommend a minimum of 4 CPUs (e.g., 2 cores with 2 hyperthreads) and 4GB of RAM. Though this is not a hard requirement, smaller configurations may slow down Sysbox-EE.
Sysbox-EE is a drop-in replacement for Sysbox, meaning that it's installed and used in the same way.
For this reason, the documents in the Sysbox repo apply equally to both Sysbox and Sysbox-EE.
Here are the links to the docs showing how to install Sysbox-EE:
Once Sysbox-EE is installed, you create a container using your container manager or orchestrator (e.g., Docker or Kubernetes) and an image of your choice.
Docker command example:
$ docker run --runtime=sysbox-runc --rm -it --hostname my_cont registry.nestybox.com/nestybox/ubuntu-bionic-systemd-docker root@my_cont:/#
Kubernetes pod spec example:
apiVersion: v1 kind: Pod metadata: name: ubu-bio-systemd-docker annotations: io.kubernetes.cri-o.userns-mode: "auto:size=65536" spec: runtimeClassName: sysbox-runc containers: - name: ubu-bio-systemd-docker image: registry.nestybox.com/nestybox/ubuntu-bionic-systemd-docker command: ["/sbin/init"] restartPolicy: Never
You can choose whatever container image you want, Sysbox-EE places no requirements on the image.
Refer to the Documentation section below for further examples on how to use Sysbox-EE.
The following documents in the Sysbox repo show how to use Docker and Kubernetes to deploy containers with Sysbox.
These docs apply equally to both Sysbox and Sysbox-EE.
Features that are specific to Sysbox-EE are tagged with "Sysbox-EE Feature Highlight" in the docs.
- Provides many examples for using Sysbox to deploy enhanced containers. New users should start here.
- Provides more detailed information on Sysbox features and troubleshooting.
In addition, the Nestybox blog site has articles on how to use Sysbox to deploy containers.
We apologize for any problems in the product or documentation, and we appreciate users filing issues that help us improve Sysbox-EE.
To file issues with Sysbox-EE (e.g., bugs, feature requests, documentation changes, etc.), please refer to the issue guidelines document.
Sysbox Enterprise customers get a guaranteed support SLA from Nestybox, and their issues and requests are prioritized.
Nestybox enhances the power of Linux containers.
We are developing software that enables containers to run any type of workload (not just micro-services), and do so easily and securely.
Our mission is to provide users with a fast, efficient, easy-to-use, and secure alternative to virtual machines for deploying virtual hosts on Linux.
We are happy to help. You can reach us at:
Slack: Nestybox Slack Workspace
We are there from Monday-Friday, 9am-5pm Pacific Time.
We thank you very much for using Sysbox-EE. We hope you find it useful.
Your trust in us is very much appreciated!
-- The Nestybox Team