Added clarity around SSL certificate format

pull/195/head
James Carppe 2021-08-11 23:17:22 +12:00
parent eb0224d770
commit 04e553c6ae
2 changed files with 2 additions and 2 deletions

View File

@ -4,7 +4,7 @@ By default, Portainers web interface and API is exposed over HTTP. This is no
## :fontawesome-solid-lock: Securing Portainer using SSL with Docker
To do so, you can use the following flags <code>--ssl</code>, <code>--sslcert</code> and <code>--sslkey</code>:
To do so, you can use the <code>--ssl</code>, <code>--sslcert</code> and <code>--sslkey</code> flags. Portainer expects certificates in PEM format.
<pre><code>$ docker run -d -p 443:9000 -p 8000:8000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v ~/local-certs:/certs -v portainer_data:/data portainer/portainer-ee:latest --ssl --sslcert /certs/portainer.crt --sslkey /certs/portainer.key</code></pre>

View File

@ -4,7 +4,7 @@ By default, Portainers web interface and API is exposed over HTTP. This is no
## :fontawesome-solid-lock: Securing Portainer using SSL with Docker
To do so, you can use the following flags <code>--ssl</code>, <code>--sslcert</code> and <code>--sslkey</code>:
To do so, you can use the <code>--ssl</code>, <code>--sslcert</code> and <code>--sslkey</code> flags. Portainer expects certificates in PEM format.
<pre><code>$ docker run -d -p 443:9000 -p 8000:8000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v ~/local-certs:/certs -v portainer_data:/data portainer/portainer-ce --ssl --sslcert /certs/portainer.crt --sslkey /certs/portainer.key</code></pre>