Skip to content

Commit 9814ed4

Browse files
committed
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 <[email protected]>
1 parent 83863a6 commit 9814ed4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/source/markdown/options/network.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Valid _mode_ values are:
1717

1818
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`.
1919

20-
- _\<network name or ID\>_**[: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. \
20+
- _\<network name or ID\>_**[: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. \
2121
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.
2222

2323
- **none**: Create a network namespace for the container but do not configure network interfaces for it, thus the container has no network connectivity.

0 commit comments

Comments
 (0)