Deduplicate more options.

Signed-off-by: Jan Kaluza <[email protected]>

Author: jankaluza

docs/source/markdown/.gitignore

@@ -34,6 +34,7 @@ podman-manifest-create.1.md
 podman-manifest-inspect.1.md
 podman-manifest-push.1.md
 podman-mount.1.md
+podman-network-create.1.md
 podman-network-ls.1.md
 podman-network-reload.1.md
 podman-pause.1.md
@@ -73,6 +74,7 @@ podman-build.unit.5.md
 podman-container.unit.5.md
 podman-image.unit.5.md
 podman-kube.unit.5.md
+podman-kube-down.1.md
 podman-network.unit.5.md
 podman-pod.unit.5.md
 podman-volume.unit.5.md

docs/source/markdown/options/all-tags.md

@@ -0,0 +1,13 @@
+####> This option file is used in:
+####>   podman podman-image.unit.5.md.in, pull
+####> If file is edited, make sure the changes
+####> are applicable to all of those.
+<< if is_quadlet >>
+### `AllTags=true`
+<< else >>
+#### **--all-tags**, **-a**
+<< endif >>
+
+All tagged images in the repository are pulled.
+
+*IMPORTANT: When using the all-tags flag, Podman does not iterate over the search registries in the **[containers-registries.conf(5)](https://github.com/containers/image/blob/main/docs/containers-registries.conf.5.md)** but always uses docker.io for unqualified image names.*

docs/source/markdown/options/annotation.image.md

@@ -1,9 +1,9 @@
 ####> This option file is used in:
-####>   podman build, farm build
+####>   podman build, podman-build.unit.5.md.in, farm build
 ####> If file is edited, make sure the changes
 ####> are applicable to all of those.
 << if is_quadlet >>
-### `Annotation=annotation=value`
+### `Annotation=annotation=value [annotation=value ...]`
 << else >>
 #### **--annotation**=*annotation=value*
 << endif >>

docs/source/markdown/options/auto-update.md

@@ -0,0 +1,11 @@
+####> This option file is used in:
+####>   podman podman-container.unit.5.md.in
+####> If file is edited, make sure the changes
+####> are applicable to all of those.
+### `AutoUpdate=registry`
+
+Indicates whether the container will be auto-updated ([podman-auto-update(1)](podman-auto-update.1.md)). The following values are supported:
+
+* `registry`: Requires a fully-qualified image reference (e.g., quay.io/podman/stable:latest) to be used to create the container. This enforcement is necessary to know which image to actually check and pull. If an image ID was used, Podman does not know which image to check/pull anymore.
+
+* `local`: Tells Podman to compare the image a container is using to the image with its raw name in local storage. If an image is updated locally, Podman simply restarts the systemd unit executing the container.

docs/source/markdown/options/configmap.md

@@ -0,0 +1,18 @@
+####> This option file is used in:
+####>   podman kube play, podman-kube.unit.5.md.in
+####> If file is edited, make sure the changes
+####> are applicable to all of those.
+<< if is_quadlet >>
+### `ConfigMap=path`
+<< else >>
+#### **--configmap**=*path*
+<< endif >>
+
+Use Kubernetes configmap YAML at path to provide a source for environment variable values within the containers of the pod.  (This option is not available with the remote Podman client)
+
+<< if is_quadlet >>
+The value may contain only one path but it may be absolute or relative to the location of the unit file.
+<< else >>
+Note: The **--configmap** option can be used multiple times or a comma-separated list of paths can be used to pass multiple Kubernetes configmap YAMLs.
+The YAML file may be in a multi-doc YAML format. But, it must contain only configmaps.
+<< endif >>

docs/source/markdown/options/disable-dns.md

@@ -0,0 +1,12 @@
+####> This option file is used in:
+####>   podman network create, podman-network.unit.5.md.in
+####> If file is edited, make sure the changes
+####> are applicable to all of those.
+<< if is_quadlet >>
+### `DisableDNS=true`
+<< else >>
+#### **--disable-dns**
+<< endif >>
+
+Disables the DNS plugin for this network which if enabled, can perform container to container name
+resolution. It is only supported with the `bridge` driver, for other drivers it is always disabled.

docs/source/markdown/options/dns.md

@@ -1,5 +1,5 @@
 ####> This option file is used in:
-####>   podman build, podman-build.unit.5.md.in, podman-container.unit.5.md.in, create, farm build, podman-network.unit.5.md.in, podman-pod.unit.5.md.in, run
+####>   podman build, podman-build.unit.5.md.in, podman-container.unit.5.md.in, create, farm build, network create, podman-network.unit.5.md.in, podman-pod.unit.5.md.in, run
 ####> If file is edited, make sure the changes
 ####> are applicable to all of those.
 << if is_quadlet >>

docs/source/markdown/options/driver.md

@@ -0,0 +1,25 @@
+####> This option file is used in:
+####>   podman network create, podman-network.unit.5.md.in
+####> If file is edited, make sure the changes
+####> are applicable to all of those.
+<< if is_quadlet >>
+### `Driver=driver`
+<< else >>
+#### **--driver**, **-d**=*driver*
+<< endif >>
+
+Driver to manage the network. Currently `bridge`, `macvlan` and `ipvlan` are supported. Defaults to `bridge`.
+As rootless the `macvlan` and `ipvlan` driver have no access to the host network interfaces because rootless networking requires a separate network namespace.
+
+The netavark backend allows the use of so called *netavark plugins*, see the
+[plugin-API.md](https://github.com/containers/netavark/blob/main/plugin-API.md)
+documentation in netavark. The binary must be placed in a specified directory
+so podman can discover it, this list is set in `netavark_plugin_dirs` in
+**[containers.conf(5)](https://github.com/containers/common/blob/main/docs/containers.conf.5.md)**
+under the `[network]` section.
+
+The name of the plugin can then be used as driver to create a network for your plugin.
+The list of all supported drivers and plugins can be seen with `podman info --format {{.Plugins.Network}}`.
+
+Note that the `macvlan` and `ipvlan` drivers do not support port forwarding. Support for port forwarding
+with a plugin depends on the implementation of the plugin.

docs/source/markdown/options/env.md

@@ -3,7 +3,7 @@
 ####> If file is edited, make sure the changes
 ####> are applicable to all of those.
 << if is_quadlet >>
-### `Environment=env`
+### `Environment=env=value [env=value ...]`
 << else >>
 #### **--env**, **-e**=*env*
 << endif >>

docs/source/markdown/options/exec.md

@@ -0,0 +1,18 @@
+####> This option file is used in:
+####>   podman podman-container.unit.5.md.in
+####> If file is edited, make sure the changes
+####> are applicable to all of those.
+### `Exec=command`
+
+Additional arguments for the container; this has exactly the same effect as passing
+more arguments after a `podman run <image> <arguments>` invocation.
+
+The format is the same as for [systemd command lines](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Command%20lines),
+However, unlike the usage scenario for similarly-named systemd `ExecStart=` verb
+which operates on the ambient root filesystem, it is very common for container
+images to have their own `ENTRYPOINT` or `CMD` metadata which this interacts with.
+
+The default expectation for many images is that the image will include an `ENTRYPOINT`
+with a default binary, and this field will add arguments to that entrypoint.
+
+Another way to describe this is that it works the same way as the [args field in a Kubernetes pod](https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell).