Add --force option to network rm subcommand

The code is similar to that used by the volume rm subcommand, however,
one difference I noticed was VolumeRemove takes the force flag/option
was a parameter. This isn't the case for NetworkRemove.

To get NetworkRemove to take a similar parameter, this would require
modifying the Docker daemon. For now this isn't a route I wish to take
when the code can be arrange to mimic the same behavior.

Co-authored-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Conner Crosby <conner@cavcrosby.tech>

2022-04-29 13:56:33 +02:00

1.4 KiB

Raw Blame History

title, description, keywords

title	description	keywords
network rm	the network rm command description and usage	network, rm, user-defined

network rm

Usage:  docker network rm NETWORK [NETWORK...]

Remove one or more networks

Aliases:
  rm, remove

Options:
  -f, --force   Do not error if the network does not exist

Description

Removes one or more networks by name or identifier. To remove a network, you must first disconnect any containers connected to it.

Examples

Remove a network

To remove the network named 'my-network':

$ docker network rm my-network

Remove multiple networks

To delete multiple networks in a single docker network rm command, provide multiple network names or ids. The following example deletes a network with id 3695c422697f and a network named my-network:

$ docker network rm 3695c422697f my-network

When you specify multiple networks, the command attempts to delete each in turn. If the deletion of one network fails, the command continues to the next on the list and tries to delete that. The command reports success or failure for each deletion.

1.4 KiB Raw Blame History