Skip to content

Commit

Permalink
README: explain that netavark is an alternative to the dnsname plugin
Browse files Browse the repository at this point in the history
This is a useful hint when the dnsname plugin is not packaged.

Signed-off-by: Gabriel de Perthuis <[email protected]>
  • Loading branch information
g2p committed May 1, 2024
1 parent a6c4263 commit 5df4e78
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,11 @@ This project focuses on:
This project only depends on:

* `podman`
* [podman dnsname plugin](https://github.com/containers/dnsname): It is usually found in the `podman-plugins` or `podman-dnsname` distro packages, those packages are not pulled by default and you need to install them. This allows containers to be able to resolve each other if they are on the same CNI network.
* [podman dnsname plugin](https://github.com/containers/dnsname): It is usually found in
the `podman-plugins` or `podman-dnsname` distro packages, those packages are not pulled
by default and you need to install them. This allows containers to be able to resolve
each other if they are on the same CNI network. This is not necessary when podman is using
netavark as a network backend.
* Python3
* [PyYAML](https://pyyaml.org/)
* [python-dotenv](https://pypi.org/project/python-dotenv/)
Expand Down

0 comments on commit 5df4e78

Please sign in to comment.