Chewing_Bever/bever-dam
Archived
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Activity

Wrote first docker-tcp script version
All checks were successful
continuous-integration/drone the build was successful
Details

Browse source
This commit is contained in:
Jef Roosens 2021-05-17 09:58:54 +02:00
parent fac578b878
commit 2cb6d2686c
Signed by: Jef Roosens
GPG key ID: B580B976584B5F30
2 changed files with 105 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

6
content/posts/docker-tcp.md
View file

@ -79,8 +79,8 @@ with the machine's public IP.
This file can now be used to generate the actual signed certificate:
```shell
openssl x509 -req -days 365 -sha256 -in server.csr -CA ca.pem -CAkey \
ca-key.pem -CAcreateserial -out server-cert.pem -extfile extfile.cnf
openssl x509 -req -days 365 -sha256 -in server.csr -CA ca.pem \
-CAkey ca-key.pem -CAcreateserial -out server-cert.pem -extfile extfile.cnf
```
Here, we can once again change the days argument to the value we want. After
@ -151,7 +151,7 @@ encrypted connection. Let's test it by adding it to Portainer!
Thankfully this is the easy part. In Portainer, add a new endpoint and choose
the "Docker" type. Pick a name for your endpoint, fill in the endpoint URL
including the port number (Docker's default port number is `2375`) and enable
including the port number (Docker's default port number is `2376`) and enable
the "TLS" switch. We choose "TLS with server and client verification", as this
is the safest. The files to upload are `ca.pem` for the TLS CA certificate,
`cert.pem` for the TLS certificate and `key.pem` for the TLS key. If all goes