mirror of
https://github.com/docker/docker-bench-security.git
synced 2025-01-31 14:22:33 +01:00
issue 145
Signed-off-by: Thomas Sjögren <konstruktoid@users.noreply.github.com>
This commit is contained in:
parent
72ba62f09c
commit
f75cb30aaa
1 changed files with 3 additions and 2 deletions
|
@ -22,11 +22,12 @@ docker run -it --net host --pid host --cap-add audit_control \
|
||||||
docker/docker-bench-security
|
docker/docker-bench-security
|
||||||
```
|
```
|
||||||
|
|
||||||
Docker bench requires Docker 1.6.2 or later in order to run, since it depends on the `--label` to exclude the current container from being inspected. If you can't upgrade to 1.6.2, feel free to remove the `--label` flag or run the shell script locally (see below).
|
Docker bench requires Docker 1.10.0 or later in order to run.
|
||||||
|
|
||||||
Additionally, there was a bug in Docker 1.6.0 that would not allow mounting `-v /dev:/dev`. If you are getting an error while accessing `resolv.conf`, please update your docker to 1.6.2.
|
|
||||||
Also note that the default image and `Dockerfile` uses `FROM: alpine` which doesn't contain `auditctl`, this will generate errors in section 1.8 to 1.18. Distribution specific Dockerfiles that fixes this issue are available in the [distros directory](https://github.com/docker/docker-bench-security/tree/master/distros).
|
Also note that the default image and `Dockerfile` uses `FROM: alpine` which doesn't contain `auditctl`, this will generate errors in section 1.8 to 1.18. Distribution specific Dockerfiles that fixes this issue are available in the [distros directory](https://github.com/docker/docker-bench-security/tree/master/distros).
|
||||||
|
|
||||||
|
The [distribution specific Dockerfiles](https://github.com/docker/docker-bench-security/tree/master/distros) may also help if the distribution you're using haven't yet shipped Docker version 1.10.0 or later.
|
||||||
|
|
||||||
## Building Docker Bench for Security
|
## Building Docker Bench for Security
|
||||||
|
|
||||||
If you wish to build and run this container yourself, you can follow the following steps:
|
If you wish to build and run this container yourself, you can follow the following steps:
|
||||||
|
|
Loading…
Reference in a new issue