libnetwork
compose-spec
Our great sponsors
libnetwork | compose-spec | |
---|---|---|
8 | 24 | |
2,120 | 2,057 | |
0.5% | 3.7% | |
3.3 | 8.4 | |
6 months ago | 5 days ago | |
Go | Dockerfile | |
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
compose-spec
-
One Minute: Compose
Specification: https://compose-spec.io
-
Podman Desktop v1.5 with Compose onboarding and enhanced Kubernetes pod data
https://github.com/compose-spec/compose-spec/blob/master/spe...
-
How “It works in my machine” turns to “It works in my container”
There are a number of incorrect statements in this post.
1) One should neither be using the "latest" nor just the "version" tag as the version can still vary depending on when it is pulled.
Instead, one should use a combination of version + hash, say alpine:3.18.2@sha256:82d1e9d7ed48a7523bdebc18cf6290bdb97b82302a8a9c27d4fe885949ea94d1 for reproducibility reasons. This provides for human readable versions as well as the specific hash.
2) Next, afaik, Compose has removed the need for version tags. All of the compose.yml files that I now use do not specify versions.
See https://github.com/compose-spec/compose-spec/blob/master/04-...
-
Telegraf Deployment Strategies with Docker Compose
Docker Compose v2 specifications provide a useful Secrets feature which may also be used for standalone Compose Application Stacks and not just in Docker Swarm mode. With Docker Secrets the environment variables that contain credentials for other subsystems are mounted into the Telegraf Container as files. These secret files are read through the Docker Secret Store plugin and passed to the respective plugins in a relatively safe manner. By using the Docker Secret Store Plugin, one can also avoid credentials that were previously visible via environment variables, to be now hidden behind runtime secret files within the container. Standard Method with Environment Variables As an example, it is possible to pass the credentials to a plugin via the environment variable placeholder in a telegraf configuration file where the credentials for a plugin exist in a .env file (e.g. MQTT input Plugin)
-
Some options missing for me.
also the docker-compose.yml file is very picky about what you have in it and where. Please read this so you know how to format it https://github.com/compose-spec/compose-spec/blob/master/spec.md
-
Persistent Volume Claim Volume Specific Options?
As part my quadlet helper tool, podlet, I'm adding functionality to convert compose files into k8s yaml to use with quadlet as an alternative to creating a bunch of separate quadlet files, which I've also added functionality for. So I would like to be able to transform the options on compose volumes into k8s yaml. For example, using the volume.podman.io/driver annotation to change the volume driver for a specific volume if possible.
-
New Docker Goodies: Init and Watch
If you find this helpful feature, please leave your feedback and suggestions here.
-
When I create a docker-compose file to deploy multiple containers, do the different versions of each compose file matter?
The compose spec will give what you need. https://github.com/compose-spec/compose-spec/blob/master/spec.md
-
Why Does Everything Say Docker Compose is Deprecated / Dead?
Indeed, as per the compose-spec a lot of what was version specific is going away
-
A compose file visualization tool that follows compose-spec and allows you to gernerate graph in several formats.
Hello everyone, I just made a tool to visualize compose files, and all the parsing rules follow the [compose-spec](https://github.com/compose-spec/compose-spec/blob/master/spec.md). I hope this tool will help you :D
What are some alternatives?
podman-desktop-companion - Podman desktop companion
docker-pi-hole - Pi-hole in a docker container
cri-dockerd - dockerd as a compliant Container Runtime Interface for Kubernetes
psutil - Cross-platform lib for process and system monitoring in Python
firebuild - Convenience of containers, security of virtual machines
pexpect - A Python module for controlling interactive programs in a pseudo-terminal
mariadb-podman-socket-activat
SaltStack - Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
Fabtools - Tools for writing awesome Fabric files
ATW (AWS Tool Web) - Amazon AWS Web Tool (view only)