conmon
docker
| conmon | docker | |
|---|---|---|
| 4 | 1 | |
| 395 | 4 | |
| 1.5% | - | |
| 7.7 | 0.0 | |
| 6 days ago | over 9 years ago | |
| C | 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.
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.
docker
-
Podman: A Daemonless Container Engine
It is absolutely not correct that Larsson did the lion’s share. What he did was implement a Go wrapper for libdevmapper, which exposes a very low-level API. It is the Docker team that implemented devmapper-based container storage, as well as the whole storage plugin system which was now required to support more than one storage method. The original devmapper lib is utterly undocumented and Larsson’s wrapper did not fix that. So getting that feature to work was an all-consuming task and it is the Docker team that did the bulk of it.
You can see all this from the early history of the devmapper directory: https://github.com/alexlarsson/docker/commits/a14496ce891f1f...
What are some alternatives?
podman - Podman: A tool for managing OCI containers and pods.
railcar - RailCar: Rust implementation of the Open Containers Initiative oci-runtime
runc - CLI tool for spawning and running containers according to the OCI specification
pq - a command-line Protobuf parser with Kafka support and JSON output
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
toolbox - Tool for interactive command line environments on Linux
distribution-spec - OCI Distribution Specification
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
go - The Go programming language
hub-feedback - Feedback and bug reports for the Docker Hub