From 5df4e786ee8c75bd8e523737571fdc6ae5655507 Mon Sep 17 00:00:00 2001 From: Gabriel de Perthuis Date: Thu, 20 Jul 2023 19:47:46 +0200 Subject: [PATCH] README: explain that netavark is an alternative to the dnsname plugin This is a useful hint when the dnsname plugin is not packaged. Signed-off-by: Gabriel de Perthuis --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 524a3277..ce190a11 100644 --- a/README.md +++ b/README.md @@ -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/)