From 9814ed40c730aa31d5f3b30bd80f200f79ef116d Mon Sep 17 00:00:00 2001 From: Paul Holzinger Date: Fri, 28 Jun 2024 16:20:24 +0200 Subject: [PATCH] docs: --network remove missing leading sentence This senetence does not add any value and instead confuses users as it suggest that the name is somhow special and related to bridge networks which is not the case. Using either the name or id is fine as described in the sentence before. Signed-off-by: Paul Holzinger --- docs/source/markdown/options/network.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/markdown/options/network.md b/docs/source/markdown/options/network.md index 8a63e2d323..2e67cc0df6 100644 --- a/docs/source/markdown/options/network.md +++ b/docs/source/markdown/options/network.md @@ -17,7 +17,7 @@ Valid _mode_ values are: For example, to set a static ipv4 address and a static mac address, use `--network bridge:ip=10.88.0.10,mac=44:33:22:11:00:99`. -- _\_**[:OPTIONS,...]**: Connect to a user-defined network; this is the network name or ID from a network created by **[podman network create](podman-network-create.1.md)**. Using the network name implies the bridge network mode. It is possible to specify the same options described under the bridge mode above. Use the **--network** option multiple times to specify additional networks. \ +- _\_**[:OPTIONS,...]**: Connect to a user-defined network; this is the network name or ID from a network created by **[podman network create](podman-network-create.1.md)**. It is possible to specify the same options described under the bridge mode above. Use the **--network** option multiple times to specify additional networks. \ For backwards compatibility it is also possible to specify comma-separated networks on the first **--network** argument, however this prevents you from using the options described under the bridge section above. - **none**: Create a network namespace for the container but do not configure network interfaces for it, thus the container has no network connectivity.