podman-deb
bypass4netns
| podman-deb | bypass4netns | |
|---|---|---|
| 1 | 3 | |
| 6 | 110 | |
| - | 6.4% | |
| 10.0 | 8.6 | |
| almost 2 years ago | 5 days ago | |
| Shell | Go | |
| - | 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-deb
-
Podman 4.2.0
> I was looking at this just last night and the story with Ubuntu is horrible. That's essentially going to be stuck on v3.4 for ten years because it's "a lot of work" to get into that distribution.
They used to provide relatively recent builds in their kubic repos. Unfortunately, for some reason, they decided to discontinue it[0]. They mentioned some CVEs or something in some issues raised around this, but to me that means pushing a new version/build and not discontinuing it.
Anyway, one of the members of the Containers org provides unstable kubic repos[1][2] for non RH systems. Unfortunately, this includes RCs, and non-stable versions, which is fine to get bleeding edge, but I'd rather just have the stable versions.
Due to the above, I've written some scripts to build deb packages for all the latest stable versions. So hopefully you can simply download the deb from GH releases[3] and then `dpkg -i *.deb && apt-get install -f`.
[0] https://podman.io/blogs/2022/04/05/ubuntu-2204-lts-kubic.htm...
[1] https://github.com/containers/podman/issues/14302#issuecomme...
[2] https://build.opensuse.org/project/show/devel:kubic:libconta...
[3] https://github.com/hoshsadiq/podman-deb/releases
bypass4netns
-
How to run an Nginx container with socket activation and rootless Podman? (I only got it working with a simplified Nginx container image)
Socket activation should be the fastest alternative as then there is no need to process and interpret the network traffic that is sent over the socket. Both slirp4netns and netavark process the traffic. If I understand correctly the network driver bypass4netns could have similar performance as socket activation. The current bypass4netns implementation has some security problems but it seems that could be fixed.
-
Podman 4.2.0
(That could a be cool feature)
Also interesting would be to fix the security considerations of using bypass4netns:
"However, it is probably possible to connect to host loopback IPs by exploiting TOCTOU of struct sockaddr * pointers."
There seems to be an implementation idea for how the problem could be fixed:
https://github.com/rootless-containers/bypass4netns/issues/2...
-
Minikube now supports rootless podman driver for running Kubernetes
The filesystem performance degradation was resolved in kernel 5.11 which added support for rootless overlayfs.
The network performance is caused by slirp (usermode TCP/IP) but it is being resolved too : https://github.com/rootless-containers/bypass4netns
What are some alternatives?
Fedora-Remix-for-WSL - Fedora Remix for Windows Subsystem for Linux.
podman-nginx-socket-activation - Demo of how to run socket-activated nginx with Podman
systemd - The systemd System and Service Manager
docker-nginx - Official NGINX Dockerfiles
FedoraWSL - Fedora as a WSL Instance. Supports multiple install.
gitlab
buildah - A tool that facilitates building OCI images.
kubernetes - Production-Grade Container Scheduling and Management
rusty-hermit - Hermit for Rust. [Moved to: https://github.com/hermit-os/hermit-rs]
unikraft - A next-generation cloud native kernel designed to unlock best-in-class performance, security primitives and efficiency savings.