Git/testssl.sh
1
0
Fork 0
mirror of https://github.com/drwetter/testssl.sh.git synced 2025-06-06 07:08:35 +02:00
Code Issues Packages Projects Releases Wiki Activity

Clarify GHCR

Browse Source
This commit is contained in:
Dirk Wetter 2025-04-06 20:31:21 +02:00 committed by GitHub
parent 56908d3a94
commit 84c1cdca1b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions

6
Dockerfile.md

@ -32,7 +32,7 @@ docker run -t mytestssl --help
docker run --rm -t mytestssl -p --header example.com docker run --rm -t mytestssl -p --header example.com
``` ```
### From dockerhub or ghcr ### From dockerhub or GHCR
You can pull the image from dockerhub or ghcr and e.g run: You can pull the image from dockerhub or ghcr and e.g run:
@ -40,7 +40,7 @@ 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 docker run --rm -t drwetter/testssl.sh:3.0 --protocols --server-preference example.com
``` ```
respectively. respectively
``` ```
docker run --rm -it ghcr.io/testssl/testssl.sh:3.0 --protocols --server-preference example.com docker run --rm -it ghcr.io/testssl/testssl.sh:3.0 --protocols --server-preference example.com
@ -48,7 +48,7 @@ docker run --rm -it ghcr.io/testssl/testssl.sh:3.0 --protocols --server-preferen
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. 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``. ``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.: 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.: