GuillaumeHemmen/docker-bench-security
1
0
Fork 0
mirror of https://github.com/docker/docker-bench-security.git synced 2025-01-19 00:32:34 +01:00
Code Issues Projects Releases Packages Wiki Activity

Minor clarification

Browse source 
i spent too many seconds pondering whether non-systemd OSs are supported. Using "might" instead of "may" removes the ambiguity.

Signed-off-by: Lorens Kockum <LorensK@users.noreply.github.com>
This commit is contained in:
LorensK 2017-03-13 12:13:24 +01:00 committed by Lorens Kockum
parent 8d1174d569
commit e1fcdb8c3d
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -18,7 +18,7 @@ We packaged docker bench as a small container for your convenience. Note that
this container is being run with a *lot* of privilege -- sharing the host's this container is being run with a *lot* of privilege -- sharing the host's
filesystem, pid and network namespaces, due to portions of the benchmark filesystem, pid and network namespaces, due to portions of the benchmark
applying to the running host. Don't forget to adjust the shared volumes applying to the running host. Don't forget to adjust the shared volumes
according to your operating system, it may not for example use systemd. according to your operating system, for example it might not use systemd.
The easiest way to run your hosts against the Docker Bench for Security is by The easiest way to run your hosts against the Docker Bench for Security is by
running our pre-built container: running our pre-built container: