Merge pull request #16732 from flouthoc/network-update

network: add support for `podman network update` and `--network-dns-server`
This commit is contained in:
OpenShift Merge Robot
2023-01-12 12:18:14 -05:00
committed by GitHub
16 changed files with 320 additions and 16 deletions

View File

@ -24,6 +24,10 @@ release because it is used as a special network mode in **podman run/create --ne
Disables the DNS plugin for this network which if enabled, can perform container to container name
resolution.
#### **--dns**=*ip*
Set network-scoped DNS resolver/nameserver for containers in this network. If not set, the host servers from `/etc/resolv.conf` will be used. It can be overwritten on the container level with the `podman run/create --dns` option. This option can be specified multiple times to set more than one IP.
#### **--driver**, **-d**
Driver to manage the network. Currently `bridge`, `macvlan` and `ipvlan` are supported. Defaults to `bridge`.

View File

@ -0,0 +1,36 @@
% podman-network-update 1
## NAME
podman\-network\-update - Update an existing Podman network
## SYNOPSIS
**podman network update** [*options*] *network*
## DESCRIPTION
Allow changes to existing container networks. At present, only changes to the DNS servers in use by a network is supported.
NOTE: Only supported with the netavark network backend.
## OPTIONS
#### **--dns-add**
Accepts array of DNS resolvers and add it to the existing list of resolvers configured for a network.
#### **--dns-drop**
Accepts array of DNS resolvers and removes them from the existing list of resolvers configured for a network.
## EXAMPLE
Update a network
```
$ podman network update network1 --dns-add 8.8.8.8,1.1.1.1
```
Update a network and add/remove dns servers
```
$ podman network update network1 --dns-drop 8.8.8.8 --dns-add 3.3.3.3
```
## SEE ALSO
**[podman(1)](podman.1.md)**, **[podman-network(1)](podman-network.1.md)**, **[podman-network-inspect(1)](podman-network-inspect.1.md)**, **[podman-network-ls(1)](podman-network-ls.1.md)**

View File

@ -32,6 +32,7 @@ so networks have to be created again after a backend change.
| prune | [podman-network-prune(1)](podman-network-prune.1.md) | Remove all unused networks |
| reload | [podman-network-reload(1)](podman-network-reload.1.md) | Reload network configuration for containers |
| rm | [podman-network-rm(1)](podman-network-rm.1.md) | Remove one or more networks |
| update | [podman-network-upate(1)](podman-network-update.1.md) | Update an existing Podman network |
## SEE ALSO
**[podman(1)](podman.1.md)**, **[containers.conf(5)](https://github.com/containers/common/blob/main/docs/containers.conf.5.md)**