podman-networking-docs
conmon
podman-networking-docs | conmon | |
---|---|---|
2 | 4 | |
22 | 401 | |
- | 3.0% | |
6.2 | 7.7 | |
17 days ago | 5 days ago | |
C | ||
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.
podman-networking-docs
-
Show HN: Obligator – An OpenID Connect server for self-hosters
Here are some documentation and demos from me and others if you're interested:
https://github.com/eriksjolund/podman-networking-docs
- Which alternative for slirp4netns in rootless containers is better?
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?
podman-nginx-socket-activation - Demo of how to run socket-activated nginx with Podman
podman - Podman: A tool for managing OCI containers and pods.
podman-static - static podman binaries and container image
runc - CLI tool for spawning and running containers according to the OCI specification
podman-socket-activated-services - Various podman container services configured to support running with systemd socket-activation
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
podman-rootful-network - Rootful Networking with Rootless Podman Containers
docker - Docker - the open-source application container engine
warp-systemd - Socket activation and other systemd integration for the Warp web server (WAI)
distribution-spec - OCI Distribution Specification
zitadel - ZITADEL - The best of Auth0 and Keycloak combined. Built for the serverless era.
go - The Go programming language