Thomas Sjögren

I was thinking the same, `python3-vagrant`?, but is a updated fork The Correct Way(tm) of doing it?

> I was thinking the same, `python3-vagrant`?, but is a updated fork The Correct Way(tm) of doing it? Will start working on https://github.com/konstruktoid/python3-vagrant but we'll see how it progresses.

Maybe a Necro warning, but https://github.com/konstruktoid/python3-vagrant is now up-to-date and all tests pass.

`winrm` command and `winrm-config` has been added to https://github.com/konstruktoid/python3-vagrant

Thanks @fbinliu for reporting this. Will check ASAP.

Hi again, the `icc` test is 2.2 (https://github.com/docker/docker-bench-security/blob/master/tests/2_docker_daemon_configuration.sh#L24-L44). Are you using the Docker container or running the script?

Ah, I just noticed that you're using 1.3.4 which is an obsolete version. See https://github.com/docker/docker-bench-security/issues/405 and please try using the shell script instead.

I can't reproduce this. Could you repeat the same steps and paste the output? ``` $ cat /etc/docker/daemon.json { "icc": false } $ docker network ls --quiet | xargs docker...

> $ cat daemon.json | grep icc > "icc": false, It shouldn't really matter if it's on WSL since the `daemon.json` is a basic JSON file. Can you run the...

That might be the issue, since https://github.com/docker/docker-bench-security/blob/master/functions/helper_lib.sh#L100 only checks the config file if defined using `--config-file` or the default `/etc/docker/daemon.json`.