add --cap-add=NET_ADMIN to make a new network device
inspired by #9452 Docker-DCO-1.1-Signed-off-by: Sven Dowideit <SvenDowideit@docker.com> (github: SvenDowideit) Signed-off-by: Sven Dowideit <SvenDowideit@docker.com>master
parent
f96a52c955
commit
c5e525eb4c
|
@ -360,6 +360,10 @@ operator wants to have all capabilities but `MKNOD` they could use:
|
||||||
For interacting with the network stack, instead of using `--privileged` they
|
For interacting with the network stack, instead of using `--privileged` they
|
||||||
should use `--cap-add=NET_ADMIN` to modify the network interfaces.
|
should use `--cap-add=NET_ADMIN` to modify the network interfaces.
|
||||||
|
|
||||||
|
$ docker run -t -i --rm ubuntu:14.04 ip link add dummy0 type dummy
|
||||||
|
RTNETLINK answers: Operation not permitted
|
||||||
|
$ docker run -t -i --rm --cap-add=NET_ADMIN ubuntu:14.04 ip link add dummy0 type dummy
|
||||||
|
|
||||||
If the Docker daemon was started using the `lxc` exec-driver
|
If the Docker daemon was started using the `lxc` exec-driver
|
||||||
(`docker -d --exec-driver=lxc`) then the operator can also specify LXC options
|
(`docker -d --exec-driver=lxc`) then the operator can also specify LXC options
|
||||||
using one or more `--lxc-conf` parameters. These can be new parameters or
|
using one or more `--lxc-conf` parameters. These can be new parameters or
|
||||||
|
|
Loading…
Reference in New Issue