libnetwork
Moby
Our great sponsors
libnetwork | Moby | |
---|---|---|
8 | 212 | |
2,120 | 67,716 | |
0.5% | 0.4% | |
3.3 | 10.0 | |
6 months 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.
libnetwork
-
Docker Networking: A Step-by-Step Guide for Developers
Container network model is a standard proposed by Docker that provides a well-defined interface or API that helps in establishing connections between containers and network plugins. Libnetwork is the native Go implementation of the CNM for connecting containers. It provides an interface between the Docker engine and network drivers. It is built on 3 main components: Sandbox, Endpoint, Network
-
Podman 4.0.0
Thanks! It seems that netavark uses macvlan to avoid creating bridge devices. Although it can also use bridges, and it seems that Docker is adding macvlan support too: https://github.com/moby/libnetwork/blob/master/docs/macvlan....
- The docker plugin API documentation is basically nonexistent
- Dedicated Ipv6 to each container
-
Is Docker Swarm broken?
I'm having an issue with docker daemon crashing only when using overlay networks. May 21 05:54:59 svr dockerd[13153]: time="2021-05-21T05:54:59.535581254-03:00" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint e8t3rwhuv3r0llsv43rup41vr ab46637f5a936ecc74bc6216601b4df118e758c02512e31a477466cd72c99526], retrying...." this error deleted my network and then crashed all the containers that were using it, container State: "Error": "failed to get network during CreateEndpoint: network e8t3rwhuv3r0llsv43rup41vr not found", "ExitCode": 128, sometimes it exits with code 0 and 143 too I found this similar issue, but it seems abandoned https://github.com/moby/libnetwork/issues/2341
- Pihole DNS does not work in WireGuard when both are in separate docker containers on the same machine
- Docker breaks IPv6 binding in patch update
Moby
-
Release Radar • March 2024 Edition
Having been featured in our February 2023, and January 2024 Release Radars, Moby is the original Linux Container runtime. This new version adds a bunch of changes to the Docker CLI and Moby itself with additional features. There's bug fixes and enhancements, with the main thing for users to be on the look out for containers that were created using Docker Engine 25.0.0. These containers might have duplicate MAC addresses, and thus must be recreated. The same goes for those containers created with Moby 25.0+ and with user defined MAC addresses. Read up on all these changes in the release notes.
-
Choosing a Name for Your Computer
Formlabs does this as well for their 3d printers, my earliest encounter of this was when Docker started getting popular: https://github.com/moby/moby/blob/master/pkg/namesgenerator/...
- Docker Inc. refuses to patch HIGH vulnerabilities in Docker
-
Do not install Docker Desktop on GNU/Linux systems
Try to use moby instead since that is the engine in Docker.
https://github.com/moby/moby
-
Exploring Podman: A More Secure Docker Alternative
> Podman is designed to help with this by providing stronger default security settings compared to Docker. Features like rootless containers, user namespaces, and seccomp profiles, while available in Docker, aren't enabled by default and often require extra setup.
Seccomp has been enabled by default since 2015: https://github.com/moby/moby/pull/18780
It is true that Rootless isn't enabled by default but its "extra setup" can be done with a single command (`dockerd-rootless-setuptool.sh install`)
- Moby: Block io_uring_* syscalls in default profile
- Io_uring will be blocked by default on Docker
-
OpenZFS 2.2: Block Cloning, Linux Containers, BLAKE3
Perhaps.
Thing is, https://github.com/moby/moby/blob/670bc0a46c4ca03b75f1e72f73... is using https://github.com/mistifyio/go-zfs which features code like `out, err := zfsOutput("get", "-H", key, d.Name)` (Source: https://github.com/mistifyio/go-zfs/blob/master/zfs.go#L315) to get a single zfs property.
Somebody chose to use a library as abstraction that looks good but is implemented as a MVP (nothing wrong with that). "In the future, we hope to work directly with libzfs" should have raised an alarm somewhere, though.
-
The Twelve-Factor App
AppArmor can restrict /proc and this is even used by docker: https://github.com/moby/moby/blob/master/contrib/apparmor/te...
What are some alternatives?
compose-spec - The Compose specification
podman - Podman: A tool for managing OCI containers and pods.
podman-desktop-companion - Podman desktop companion
containerd - An open and reliable container runtime
cri-dockerd - dockerd as a compliant Container Runtime Interface for Kubernetes
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
firebuild - Convenience of containers, security of virtual machines
docker-openwrt - OpenWrt running in Docker
mariadb-podman-socket-activat
ofelia - A docker job scheduler (aka. crontab for docker)
docker-pi-hole - Pi-hole in a docker container
k3d - Little helper to run CNCF's k3s in Docker