Git/testssl.sh
1
0
Fork 0
mirror of https://github.com/drwetter/testssl.sh.git synced 2025-10-31 13:55:25 +01:00
Code Issues Packages Projects Releases Wiki Activity

Resort and polish

Browse Source
This commit is contained in:
Dirk Wetter
2019-09-13 10:54:18 +02:00
committed by GitHub
parent e4e3df50eb
commit 5767e1496e
1 changed files with 12 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
Dockerfile.md
View File

@@ -10,21 +10,22 @@ You can also supply command line options like:
``docker run -t mytestssl -p --header example.com`` ``docker run -t mytestssl -p --header example.com``
Please keep in mind that any output file (--log, --html, --json etc.) will be created or pull the image from dockerhub and run:
in the container. If you wish to have this created in your local directory you can mount a volume and change the output prefix e.g.:
```bash
docker run -t -v ${PWD}:/data drwetter/testssl.sh --html --outprefix /data/ example.com
```
Also if you don't provide a user, this docker container uses a non-root user.
You can also pull the image from dockerhub and run:
``` ```
docker run -t drwetter/testssl.sh --pfs example.com docker run -t drwetter/testssl.sh --pfs example.com
``` ```
Tags supported are currently: ``latest``, ``stable`` which are all the same and point to ``3.0``. And for the indomitable users who prefer to run old stuff ``2.9.5``. The tag ``2.9dev`` should not be used. Tags supported are: ``latest``, ``stable`` which _for now_ are all the same and point to ``3.0``.
``docker run -t drwetter/testssl.sh:stable example.com``. ``docker run -t drwetter/testssl.sh:stable example.com``.
And for the indomitable users who prefer to run old stuff you can use the tag ``2.9.5``. Please note ``2.9dev`` should not be used anymore.
Keep in mind that any output file (--log, --html, --json etc.) will be created in the container. If you wish to have this created in a local directory you can mount a volume into the container and change the output prefix where the container user has write access to, e.g.:
```
docker run -t -v /tmp:/data drwetter/testssl.sh --htmlfile /data/ example.com
```
Also if you don't provide a user, testssl.sh's docker container uses a non-root user (usually with user/groupid 1000:1000).