storage
runc
storage | runc | |
---|---|---|
5 | 32 | |
526 | 11,441 | |
1.0% | 0.8% | |
9.7 | 9.3 | |
2 days ago | 2 days ago | |
Go | 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.
storage
-
Where are the containers located on my system?
Check here: https://github.com/containers/storage/blob/main/docs/containers-storage.conf.5.md
-
Storage Solutions & Their Use Cases
One example that keeps popping up over the years is containers and ZFS or more specifically Linux kernel namespaces and ZFS. First LXD in 2016, podman in 2020 and 2021. There is docker issues in the past as well with the ZFS storage driver or overlayfs. These issues are fixed rather quickly by ZFS (because they are very good at what they do) or by upstream, but bugs keep happening. It is something I do not want to deal with. As I expect future problems with ZFS and projects that depend on specific features of the linux kernel, I prefer using something else. In this case Stratis, LVM and XFS, or LVM and ext4.
-
How to mount network storage into podman rootless container?
I tried using NFS because I know it well, and it is easy to do using ZFS. This Red Hat blog post says NFS should work and it does not work at the same time. I decided to just try. The ZFS server has no idea about the subuids on the podman host, so I had to mess around with --uidmap and --gidmap. That worked, as long as I did not use a pod. To keep things neat and simple, I tried to put all my Nextcloud containers into one pod. However, the id-mapping features cannot map multiple container IDs to the same host IDs. So, I cannot map the www-data (70) user and the postgres (82) user to localadmin (1000) on the podman host. Next, I tried directly mounting the NFS share as a volume using the '--opt type=nfs4' option when creating the volumes. Right away, I learned that rootless containers can't mount network shares. Makes a certain kind of sense and is also documented in the man page. But I first tried using root containers, to prove out the concept. The volumes mounted without complaint, but I landed back at square one because the id-mapping is not applied anywhere now. Appears to me that, NFS is a complete dud for this kind of application.
- Overlay: Support Native Rootless Mounts
-
Podman: A Daemonless Container Engine
Docker is properly attributed to, see https://github.com/containers/storage/blob/a4cc7aa79e050c976...
I think OP wanted to say that Podman hates Docker what is not I feel when I'm interacting with the community there. People who use Podman do it because of it's additional features that Docker does not have, like starting an Container from a rootfs or mounting the currect directory in a container using "." as path. It's a lot of small things that make Podman better.
runc
-
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
-
Bringing Memory Safety to sudo and su - with Ferrous Systems and Tweedegolf
Not OP, but if I had to guess, a lot of this can be picked up by just observing common security issues in the Linux space, since similar mistakes and oversights have caused quite a few real-world CVEs in the past, e.g. this random example of a TOCTTOU vulnerability in runc.
- Containers - entre historia y runtimes
- [email protected]+incompatible with ubuntu 22.04 on arm64 ?
What are some alternatives?
asciinema - Platform for hosting and sharing terminal session recordings
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
go - The Go programming language
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
zfs - OpenZFS on Linux and FreeBSD
youki - A container runtime written in Rust
podman - Podman: A tool for managing OCI containers and pods.
railcar - RailCar: Rust implementation of the Open Containers Initiative oci-runtime
containerd - An open and reliable container runtime
conmon - An OCI container runtime monitor.