nvidia-container-runtime
runc


nvidia-container-runtime | runc | |
---|---|---|
3 | 35 | |
1,089 | 12,137 | |
- | 0.9% | |
0.0 | 9.4 | |
over 1 year ago | 2 days ago | |
Makefile | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nvidia-container-runtime
-
Comparing 3 Docker container runtimes - Runc, gVisor and Kata Containers
Now you can even choose a runtime which creates a virtual machine or a container with a more secure isolation. Once there was a runtime for using an NVIDIA GPU called nvidia-container-runtime. That project is now deprecated and Docker has the "--gpus" option instead. Talking about GPUs is not the scope of this blogpost, but it is a good example of a special runtime that gave additional capabilities to containers.
-
Can you add CUDA to a docker container?
Yes, you can, actually already exist images with Cuda installed https://hub.docker.com/r/nvidia/cuda . To be able to use the GPU device within the docker container you need to install `nvidia-container-runtime` https://github.com/NVIDIA/nvidia-container-runtime.
- "Unknown runtime specified nvidia" trying to configure Plex Docker container with GPU passthrough
runc
-
Installing Kubernetes using Kubeadm utility
curl -LO https://github.com/opencontainers/runc/releases/download/v1.2.2/runc.amd64 sudo install -m 755 runc.amd64 /usr/local/sbin/runc
-
Comparing 3 Docker container runtimes - Runc, gVisor and Kata Containers
Previously I wrote about the multiple variants of Docker and also the dependencies behind the Docker daemon. One of the dependencies was the container runtime called runc. That is what creates the usual containers we are all familiar with. When you use Docker, this is the default runtime, which is understandable since it was started by Docker, Inc.
-
You run containers, not dockers - Discussing Docker variants, components and versioning
Now we have dockerd which uses containerd, but containerd will not create containers directly. It needs a runtime and the default runtime is runc, but that can be changed. containerd actually doesn't have to know the parameters of the runtime. There is a shim process between containerd and runc, so containerd knows the parameters of the shim, and the shim knows the parameters of runc or other runtimes.
-
Nanos – A Unikernel
I can speak to this. Containers, and by extension k8s, break a well known security boundary that has existed for a very long time - whether you are using a real (hardware) server or a virtual machine on the cloud if you pop that instance/server generally speaking you only have access to that server. Yeh, you might find a db config with connection details if you landed on say a web app host but in general you still have to work to start popping the next N servers.
That's not the case when you are running in k8s and the last container breakout was just announced ~1 month ago: https://github.com/opencontainers/runc/security/advisories/G... .
At the end of the day it is simply not a security boundary. It can solve other problems but not security ones.
- Several container breakouts due to internally leaked fds
- Container breakout through process.cwd trickery and leaked fds
-
US Cybersecurity: The Urgent Need for Memory Safety in Software Products
It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C)
As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun) this year(https://cloud.redhat.com/blog/whats-new-in-red-hat-openshift...), which is written in C as an alternative to runc, which is written in Go(https://github.com/opencontainers/runc)...
-
Run Firefox on ChromeOS
Rabbit hole indeed. That wasn't related to my job at the time, lol. The job change came with a company-provided computer and that put an end to the tinkering.
BTW, I found my hacks to make runc run on Chromebook: https://github.com/opencontainers/runc/compare/main...gabrys...
-
Crun: Fast and lightweight OCI runtime and C library for running containers
being the main author of crun, I can clarify that statement: I am not a fan of Go _for this particular use case_.
Using C instead of Go avoided a bunch of the workarounds that exists in runc to workaround the Go runtime, e.g. https://github.com/opencontainers/runc/blob/main/libcontaine...
-
Best virtualization solution with Ubuntu 22.04
runc
What are some alternatives?
container-images
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
nvidia-docker - Build and run Docker containers leveraging NVIDIA GPUs
youki - A container runtime written in Rust
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
asciinema - Platform for hosting and sharing terminal session recordings
conmon - An OCI container runtime monitor.
containerd - An open and reliable container runtime
cni - Container Network Interface - networking for Linux containers
podman - Podman: A tool for managing OCI containers and pods.
distribution-spec - OCI Distribution Specification
dive - A tool for exploring each layer in a docker image

