FilesExpand file tree

 master

/

docker_node_rm.yaml

Copy path

Blame

More file actions

Blame

More file actions

Latest commit

 

History

History

History

48 lines (37 loc) · 1.41 KB

 master

/

docker_node_rm.yaml

Copy path

Top

File metadata and controls

• Code
• Blame

48 lines (37 loc) · 1.41 KB

Raw

Copy raw file

Download raw file

Open symbols panel

Edit and raw actions

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

command: docker node rm

aliases: remove

short: Remove one or more nodes from the swarm

long: When run from a manager node, removes the specified nodes from a swarm.

usage: docker node rm [OPTIONS] NODE [NODE...]

pname: docker node

plink: docker_node.yaml

options:

- option: force

shorthand: f

default_value: "false"

description: Force remove a node from the swarm

examples: |-

### Remove a stopped node from the swarm

```bash

$ docker node rm swarm-node-02

Node swarm-node-02 removed from swarm

```

### Attempt to remove a running node from a swarm

Removes the specified nodes from the swarm, but only if the nodes are in the

down state. If you attempt to remove an active node you will receive an error:

```non

$ docker node rm swarm-node-03

Error response from daemon: rpc error: code = 9 desc = node swarm-node-03 is not

down and can't be removed

```

### Forcibly remove an inaccessible node from a swarm

If you lose access to a worker node or need to shut it down because it has been

compromised or is not behaving as expected, you can use the `--force` option.

This may cause transient errors or interruptions, depending on the type of task

being run on the node.

```bash

$ docker node rm --force swarm-node-03

Node swarm-node-03 removed from swarm

```

A manager node must be demoted to a worker node (using `docker node demote`)

before you can remove it from the swarm.