You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Dockerfile.md
+22-7Lines changed: 22 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,21 @@
1
-
## Usage:
1
+
## Usage
2
+
3
+
### From git directory
4
+
5
+
```
6
+
docker build .
7
+
```
8
+
9
+
Catch is when you run without image tags you need to catch the ID when building
10
+
11
+
```
12
+
[..]
13
+
---> 889fa2f99933
14
+
Successfully built 889fa2f99933
15
+
```
16
+
17
+
More comfortable is
2
18
3
-
(in git directory):
4
19
```
5
20
docker build -t mytestssl .
6
21
docker run --rm -t mytestssl example.com
@@ -13,18 +28,18 @@ docker run -t mytestssl --help
13
28
docker run --rm -t mytestssl -p --header example.com
14
29
```
15
30
16
-
or pull the image from dockerhub and run:
31
+
### From dockerhub
32
+
33
+
You can pull the image from dockerhub and run:
17
34
18
35
```
19
-
docker run --rm -t drwetter/testssl.sh --pfs example.com
36
+
docker run --rm -t drwetter/testssl.sh --fs example.com
20
37
```
21
38
22
-
Tags supported are: ``latest``, ``stable``which _for now_are all the same and point to ``3.0``.
39
+
Tags supported are: ``3.1dev`` and ``latest`` are the same, i.e. is the rolling release. ``3.0`` is the latest stable version from git which might have a few improvements over the released 3.0.X.
23
40
24
41
``docker run --rm -t drwetter/testssl.sh:stable example.com``.
25
42
26
-
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.
27
-
28
43
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.:
Think of 3.1dev like a rolling release, see below. For the stable version help yourself by downloading the [ZIP](https://github.com/drwetter/testssl.sh/archive/3.0.2.zip) or [tar.gz](https://github.com/drwetter/testssl.sh/archive/3.0.2.zip) archive. Just ``cd`` to the directory created (=INSTALLDIR) and run it off there.
56
+
Think of 3.1dev like a rolling release, see below. For the stable version help yourself by downloading the [ZIP](https://codeload.github.com/drwetter/testssl.sh/zip/3.0.4) or [tar.gz](https://codeload.github.com/drwetter/testssl.sh/tar.gz/3.0.4) archive. Just ``cd`` to the directory created (=INSTALLDIR) and run it off there.
57
57
58
58
#### Docker
59
59
60
-
Testssl.sh has minimal requirements. As stated you don't have to install or build anything. You can just run it from the pulled/cloned directory. Still if you don't want to pull the github repo to your directory of choice you can pull a container from dockerhub and run it:
60
+
Testssl.sh has minimal requirements. As stated you don't have to install or build anything. You can just run it from the pulled/cloned directory. Still if you don't want to pull the github repo to your directory of choice you can pull a container from dockerhub and run it:
61
61
62
62
```
63
63
docker run --rm -ti drwetter/testssl.sh:3.1dev <your_cmd_line>
64
64
```
65
65
66
66
Or if you have cloned this repo you also can just ``cd`` to the INSTALLDIR and run
followed by ``docker run -ti <ID> <your_cmd_line>`` where ``ID`` is the identifier in the last line from the build command like
71
+
For more please consult [Dockerfile.md](https://github.com/drwetter/testssl.sh/blob/3.1dev/Dockerfile.md).
72
72
73
-
```
74
-
---> 889fa2f99933
75
-
Successfully built 889fa2f99933
76
-
```
77
73
78
74
### Status
79
75
80
76
We're currently in the development phase, version 3.1dev. 3.1dev will eventually become 3.2. Bigger features are developed in a separate branch before merged into 3.1dev to avoid hiccups or inconsistencies. Albeit we try to keep 3.1dev as solid as possible things will certainly change in 3.1dev. So if you need stability the 3.0 branch is better for you. Think of the 3.1dev branch like a rolling release.
81
77
82
-
Support for 2.9.5 has been dropped. Supported is 3.0.x only.
78
+
Support for 2.9.5 has been dropped. Supported is >= 3.0.x only.
0 commit comments