railcar
conmon
Our great sponsors
railcar | conmon | |
---|---|---|
2 | 4 | |
33 | 395 | |
- | 1.5% | |
0.0 | 7.7 | |
over 2 years ago | 2 days ago | |
Rust | C | |
GNU General Public License v3.0 or later | 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.
railcar
- Podman: A Daemonless Container Engine
-
Show HN: Vas-quod – A minimal Linux container runtime written in Rust
Nice work on this! If you cut out a bunch of the features supported by other containerization systems, the code gets quite short. My first one was in C and only a couple hundred lines. I worked on a full-featured rust container runtime while I was at Oracle. It is compatible with the oci-runtime spec, so can be used as a runtime for docker or kubernetes. The most up to date fork is at https://github.com/drahnr/railcar if you want to take a look at it for any ideas.
conmon
-
Creating Kubernetes Cluster With CRI-O
It is an open-source, community-driven project which supports OCI-based container registries. It is being maintained by contributors working in Red Hat, Intel, etc. It also comes with a monitoring program known as conmon. Conmon is an OCI container runtime monitor, which makes the communication between CRI-O and runc for a single container.
-
Which alternative for slirp4netns in rootless containers is better?
When considering using socket activation it's good to know that socket-activation has the advantage that you can create on-demand services. And in the future you might be able to do container image upgrades without loosing an active TCP connection https://github.com/containers/conmon/issues/393 (Right now it's just a feature request that I wrote).
-
Docker is dead?!? Podman - an alternative tool?
This was a wrong assumption. Podman directly uses runC or crun instead of containerd using a technology named conmon. Some more useful information can be found in this article.
-
Podman: A Daemonless Container Engine
Well, "daemonless" is kind of marketing - there is still this daemon-per-container 'conmon' thing https://github.com/containers/conmon and I don't get why it is needed because 1) who actually needs to re-attach anyway? 2) container's streams are already properly handled by whatever supervisor (e.g. systemd). You can't disable conmon and I'm not sure if its usage is not hardcoded throughout the codebase.
I would very much like to use Podman as a finally proper container launcher in production (non-FAANG scale - at which you maybe start to need k8s), but having an unnecessary daemon moving part in thousands lines of C makes me frown so far.
What are some alternatives?
vas-quod - :aerial_tramway: Minimal linux container runtime
podman - Podman: A tool for managing OCI containers and pods.
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
runc - CLI tool for spawning and running containers according to the OCI specification
docker - Docker - the open-source application container engine
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
distribution-spec - OCI Distribution Specification
enroot - A simple yet powerful tool to turn traditional container/OS images into unprivileged sandboxes.
go - The Go programming language