mirror of
https://github.com/containers/podman.git
synced 2025-08-06 03:19:52 +08:00
drop support for "pasta" as a network name
The pasta network mode has been added in podman v4.4 and this causes a conflict with named networks that could also be called "pasta". To not break anything we had special logic to prefer the named network over the network mode. Now with 5.0 we can break this and remove this awkward special handling from the code. Containers created with 4.X that use a named network pasta will also continue to work fine, this chnage will only effect the creation of new containers with a named network pasta and instead always used the network mode pasta. We now also block the creation of networks with the name "pasta". Signed-off-by: Paul Holzinger <pholzing@redhat.com>
This commit is contained in:
@ -15,11 +15,6 @@ If no options are provided, Podman assigns a free subnet and name for the networ
|
||||
|
||||
Upon completion of creating the network, Podman displays the name of the newly added network.
|
||||
|
||||
NOTE: The support for "pasta" as network *name* value is deprecated and will not be accepted in the next major
|
||||
Podman version 5.0, because it is used as a special network mode in **podman run/create --network**.
|
||||
The CNI backend is also deprecated and will also be removed in the next major Podman version 5.0, in preference
|
||||
of Netavark, see **[podman-network(1)](podman-network.1.md)** on how to change the backend.
|
||||
|
||||
## OPTIONS
|
||||
#### **--disable-dns**
|
||||
|
||||
|
Reference in New Issue
Block a user