Files
testssl.sh/Dockerfile.md
Dirk Wetter 84c1cdca1b Clarify GHCR
2025-04-06 20:31:21 +02:00

60 lines
1.7 KiB
Markdown

## Usage
### From git directory
```
git checkout 3.0
git pull
docker build .
```
Catch is when you run without image tags you need to catch the ID when building
```
[..]
---> 889fa2f99933
Successfully built 889fa2f99933
```
More comfortable is
```
git checkout 3.0
git pull
docker build -t mytestssl .
docker run --rm -t mytestssl example.com
```
You can also supply command line options like:
```
docker run -t mytestssl --help
docker run --rm -t mytestssl -p --header example.com
```
### From dockerhub or GHCR
You can pull the image from dockerhub or ghcr and e.g run:
```
docker run --rm -t drwetter/testssl.sh:3.0 --protocols --server-preference example.com
```
respectively
```
docker run --rm -it ghcr.io/testssl/testssl.sh:3.0 --protocols --server-preference example.com
```
As of now other tags supported are: ``latest`` or ``3.2``.. They are the same, i.e. the stable version. ``3.0`` is the old stable version.
``docker run --rm -t drwetter/testssl.sh:3.0 example.com`` or, for GHCR: ``docker run --rm -t ghcr.io/testssl/testssl.sh:3.0 example.com``.
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 on your host 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 --rm -t -v /tmp:/data drwetter/testssl.sh:3.0 --htmlfile /data/ example.com
```
which writes the HTML output to ``/tmp/example.com_p443-<date>-<time>.html.`` The uid/gid is the one from the docker user but normally the file is 644. testssl.sh's docker container uses a non-root user (usually with user/groupid 1000:1000).