mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 12:38:05 +00:00
Fix utf8/links/shell
This commit is contained in:
Sebastiaan van Steenis
committed by
Mark Bishop
Mark Bishop
parent
c9e44be5c2
commit
f88022b6b2
@@ -153,7 +153,7 @@ RKE uses a `.yml` config file to install and configure your Kubernetes cluster.
|
||||
|
||||
- [Template for using Self Signed Certificate (3-node-externalssl-certificate.yml)](https://raw.githubusercontent.com/rancher/rancher/58e695b51096b1f404188379cea6f6a35aea9e4c/rke-templates/3-node-externalssl-certificate.yml)
|
||||
- [Template for using Certificate Signed By A Recognized Certificate Authority (3-node-externalssl-recognizedca.yml)](https://raw.githubusercontent.com/rancher/rancher/58e695b51096b1f404188379cea6f6a35aea9e4c/rke-templates/3-node-externalssl-recognizedca.yml)
|
||||
2. Rename the file `rancher-cluster.yml`.
|
||||
2. Rename the file to `rancher-cluster.yml`.
|
||||
|
||||
## Part 6-Configure Nodes
|
||||
|
||||
@@ -208,6 +208,9 @@ In the `kind: Secret` with `name: cattle-keys-server`:
|
||||
|
||||
After replacing the value, the file should look like the example below (the base64 encoded string should be different):
|
||||
|
||||
>**Note:**
|
||||
> The base64 encoded string should be on the same line as `cacerts.pem`, without any newline at the beginning, in between or at the end.
|
||||
|
||||
```
|
||||
---
|
||||
apiVersion: v1
|
||||
@@ -226,13 +229,13 @@ If you are using a Certificate Signed By A Recognized Certificate Authority, you
|
||||
|
||||
## Part 8-Configure FQDN
|
||||
|
||||
There is 1 reference to `<FQDN>` in the config file. This needs to be replaced with the FQDN chosen in [Configure DNS](#configure-dns).
|
||||
There is 1 reference to `<FQDN>` in the config file. This needs to be replaced with the FQDN chosen in [Configure DNS](#part-3-configure-dns).
|
||||
|
||||
In the `kind: Ingress` with `name: cattle-ingress-http`:
|
||||
|
||||
* Replace `<FQDN>` with the FQDN chosen in [Configure DNS](#configure-dns).
|
||||
* Replace `<FQDN>` with the FQDN chosen in [Configure DNS](#part-3-configure-dns).
|
||||
|
||||
After replacing `<FQDN>` with the FQDN chosen in [Configure DNS](#configure-dns), the file should look like the example below (`rancher.yourdomain.com` is the FQDN used in this example):
|
||||
After replacing `<FQDN>` with the FQDN chosen in [Configure DNS](#part-3-configure-dns), the file should look like the example below (`rancher.yourdomain.com` is the FQDN used in this example):
|
||||
|
||||
```
|
||||
---
|
||||
@@ -288,7 +291,7 @@ INFO[0000] [network] Pulling image [alpine:latest] on host [1.1.1.1]
|
||||
...
|
||||
INFO[0101] Finished building Kubernetes cluster successfully
|
||||
```
|
||||
## Part 11—Backup kube_config_rancher-cluster.yml
|
||||
## Part 11-Backup kube_config_rancher-cluster.yml
|
||||
|
||||
During installation, RKE generates a config file named `kube_config_rancher-cluster.yml` in the same directory as the RKE binary. Copy this file and back it up to a safe location. You'll use this file later when upgrading Rancher Server.
|
||||
|
||||
@@ -296,7 +299,7 @@ During installation, RKE generates a config file named `kube_config_rancher-clus
|
||||
|
||||
**For those using a certificate signed by a recognized CA:**
|
||||
|
||||
>**Note:** If you're using a self-signed certificate, you don't have to complete this part. Continue to [What's Next?](#whats-next).
|
||||
>**Note:** If you're using a self-signed certificate, you don't have to complete this part. Continue to [What's Next?](#what-s-next).
|
||||
|
||||
By default, Rancher automatically generates self-signed certificates for itself after installation. However, since you've provided your own certificates, you must disable the certificates that Rancher generated for itself.
|
||||
|
||||
@@ -308,4 +311,4 @@ By default, Rancher automatically generates self-signed certificates for itself
|
||||
|
||||
## What's Next?
|
||||
|
||||
Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN chosen in [Configure DNS](#configure-dns).
|
||||
Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN chosen in [Configure DNS](#part-3-configure-dns).
|
||||
|
||||
@@ -127,7 +127,10 @@ stream {
|
||||
Besides installing NGINX as a package on the operating system, you can also run it as a Docker container. Save the edited **Example NGINX config** as `/etc/nginx.conf` and run the following command to launch the NGINX container:
|
||||
|
||||
```
|
||||
docker run -p 80:80 -p 443:443 -v /etc/nginx.conf:/etc/nginx/nginx.conf -d nginx:1.14
|
||||
docker run -d --restart=unless-stopped \
|
||||
-p 80:80 -p 443:443 \
|
||||
-v /etc/nginx.conf:/etc/nginx/nginx.conf \
|
||||
nginx:1.14
|
||||
```
|
||||
|
||||
## Part 3-Configure DNS
|
||||
@@ -155,7 +158,7 @@ From your workstation, open a web browser and navigate to our [RKE Releases](htt
|
||||
|
||||
Make the RKE binary that you just downloaded executable. Open Terminal, change directory to the location of the RKE binary, and then run the following command:
|
||||
|
||||
``` bash
|
||||
```
|
||||
# MacOS
|
||||
$ chmod +x rke_darwin-amd64
|
||||
# Linux
|
||||
@@ -184,7 +187,7 @@ RKE uses a `.yml` config file to install and configure your Kubernetes cluster.
|
||||
|
||||
- [Template for using Self Signed Certificate (3-node-certificate.yml)](https://raw.githubusercontent.com/rancher/rancher/e9d29b3f3b9673421961c68adf0516807d1317eb/rke-templates/3-node-certificate.yml)
|
||||
- [Template for using Certificate Signed By A Recognized Certificate Authority (3-node-certificate-recognizedca.yml)](https://raw.githubusercontent.com/rancher/rancher/e9d29b3f3b9673421961c68adf0516807d1317eb/rke-templates/3-node-certificate-recognizedca.yml)
|
||||
2. Rename the file `rancher-cluster.yml`.
|
||||
2. Rename the file to `rancher-cluster.yml`.
|
||||
|
||||
## Part 6-Configure Nodes
|
||||
|
||||
@@ -229,7 +232,7 @@ Certificates can be configured by using base64 encoded strings in the config fil
|
||||
### Option A-Self Signed Certificate
|
||||
|
||||
>**Note:**
|
||||
> If you are using Certificate Signed By A Recognized Certificate Authority, [click here](#certificate-signed-by-a-recognized-certificate-authority) to proceed.
|
||||
> If you are using Certificate Signed By A Recognized Certificate Authority, [click here](#option-b-certificate-signed-by-a-recognized-certificate-authority) to proceed.
|
||||
|
||||
If you are using a Self Signed Certificate, you will need to generate base64 encoded strings for each of your files (Certificate file, Certificate Key file, and CA certificate file). Make sure that your certificate file includes all the intermediate certificates in the chain, the order of certificates in this case is first your own certificate, followed by the intermediates.
|
||||
|
||||
@@ -240,6 +243,9 @@ In the `kind: Secret` with `name: cattle-keys-ingress`:
|
||||
|
||||
After replacing the values, the file should look like the example below (the base64 encoded strings should be different):
|
||||
|
||||
>**Note:**
|
||||
> The base64 encoded string should be on the same line as `tls.crt` or `tls.key`, without any newline at the beginning, in between or at the end.
|
||||
|
||||
```
|
||||
---
|
||||
apiVersion: v1
|
||||
@@ -259,6 +265,9 @@ In the `kind: Secret` with `name: cattle-keys-server`:
|
||||
|
||||
After replacing the value, the file should look like the example below (the base64 encoded string should be different):
|
||||
|
||||
>**Note:**
|
||||
> The base64 encoded string should be on the same line as `cacerts.pem`, without any newline at the beginning, in between or at the end.
|
||||
|
||||
```
|
||||
---
|
||||
apiVersion: v1
|
||||
@@ -282,6 +291,9 @@ In the `kind: Secret` with `name: cattle-keys-ingress`:
|
||||
|
||||
After replacing the values, the file should look like the example below (the base64 encoded strings should be different):
|
||||
|
||||
>**Note:**
|
||||
> The base64 encoded string should be on the same line as `tls.crt` or `tls.key`, without any newline at the beginning, in between or at the end.
|
||||
|
||||
```
|
||||
---
|
||||
apiVersion: v1
|
||||
@@ -297,13 +309,13 @@ data:
|
||||
|
||||
## Part 8-Configure FQDN
|
||||
|
||||
There are 2 references to `<FQDN>` in the config file. Both need to be replaced with the FQDN chosen in [Configure DNS](#configure-dns).
|
||||
There are 2 references to `<FQDN>` in the config file. Both need to be replaced with the FQDN chosen in [Configure DNS](#part-3-configure-dns).
|
||||
|
||||
In the `kind: Ingress` with `name: cattle-ingress-http`:
|
||||
|
||||
* Replace `<FQDN>` with the FQDN chosen in [Configure DNS](#configure-dns).
|
||||
* Replace `<FQDN>` with the FQDN chosen in [Configure DNS](#part-3-configure-dns).
|
||||
|
||||
After replacing `<FQDN>` wit the FQDN chosen in [Configure DNS](#configure-dns), the file should look like the example below (`rancher.yourdomain.com` is the FQDN used in this example):
|
||||
After replacing `<FQDN>` wit the FQDN chosen in [Configure DNS](#part-3-configure-dns), the file should look like the example below (`rancher.yourdomain.com` is the FQDN used in this example):
|
||||
|
||||
```
|
||||
---
|
||||
@@ -364,7 +376,7 @@ INFO[0000] [network] Pulling image [alpine:latest] on host [1.1.1.1]
|
||||
INFO[0101] Finished building Kubernetes cluster successfully
|
||||
```
|
||||
|
||||
## Part 11—Backup kube_config_rancher-cluster.yml
|
||||
## Part 11-Backup kube_config_rancher-cluster.yml
|
||||
|
||||
During installation, RKE generates a config file named `kube_config_rancher-cluster.yml` in the same directory as the RKE binary. Copy this file and back it up to a safe location. You'll use this file later when upgrading Rancher Server.
|
||||
|
||||
@@ -372,7 +384,7 @@ During installation, RKE generates a config file named `kube_config_rancher-clus
|
||||
|
||||
**For those using a certificate signed by a recognized CA:**
|
||||
|
||||
>**Note:** If you're using a self-signed certificate, you don't have to complete this part. Continue to [What's Next?](#whats-next).
|
||||
>**Note:** If you're using a self-signed certificate, you don't have to complete this part. Continue to [What's Next?](#what-s-next).
|
||||
|
||||
By default, Rancher automatically generates self-signed certificates for itself after installation. However, since you've provided your own certificates, you must disable the certificates that Rancher generated for itself.
|
||||
|
||||
@@ -384,4 +396,4 @@ By default, Rancher automatically generates self-signed certificates for itself
|
||||
|
||||
## What's Next?
|
||||
|
||||
Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN chosen in [Configure DNS](#configure-dns).
|
||||
Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN chosen in [Configure DNS](#part-3-configure-dns).
|
||||
|
||||
@@ -10,4 +10,4 @@ You can find Rancher images at [DockerHub](https://hub.docker.com/r/rancher/ranc
|
||||
|
||||
- `rancher/rancher:stable`: Our newest stable release. This tag is recommended for production.
|
||||
|
||||
Any tag with a `-rc` or another suffix is meant for the {{< product >}} testing team to validate. You should not use these tags, as these builds are not officially supported.
|
||||
The `master` tag or any tag with a `-rc` or another suffix is meant for the {{< product >}} testing team to validate. You should not use these tags, as these builds are not officially supported.
|
||||
|
||||
@@ -30,8 +30,7 @@ Installation of Rancher on a single node with an external load balancer involves
|
||||
If you chose [Option B](#option-b-bring-your-own-certificate-signed-by-recognized-ca) as your SSL option, log into the Rancher UI and remove the certificates that Rancher automatically generates.
|
||||
|
||||
|
||||
|
||||
## Part 1—Provision Linux Host
|
||||
## Part 1-Provision Linux Host
|
||||
|
||||
Provision a single Linux host to launch your {{< product >}} Server.
|
||||
|
||||
@@ -45,16 +44,16 @@ Provision a single Linux host to launch your {{< product >}} Server.
|
||||
|
||||
{{< note_server-tags >}}
|
||||
|
||||
## Part 2—Choose an SSL Option and Install Rancher
|
||||
## Part 2-Choose an SSL Option and Install Rancher
|
||||
|
||||
For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster.
|
||||
|
||||
You can choose from the following scenarios:
|
||||
|
||||
- [Option A—Bring Your Own Certificate: Self-Signed](#option-a-bring-your-own-certificate-self-signed)
|
||||
- [Option B—Bring Your Own Certificate: Signed by Recognized CA](#option-b-bring-your-own-certificate-signed-by-recognized-ca)
|
||||
- [Option A-Bring Your Own Certificate: Self-Signed](#option-a-bring-your-own-certificate-self-signed)
|
||||
- [Option B-Bring Your Own Certificate: Signed by Recognized CA](#option-b-bring-your-own-certificate-signed-by-recognized-ca)
|
||||
|
||||
### Option A—Bring Your Own Certificate: Self-Signed
|
||||
### Option A-Bring Your Own Certificate: Self-Signed
|
||||
|
||||
If you elect to use a self-signed certificate to encrypt communication, you must install the certificate on your load balancer (which you'll do later) and your Rancher container. Run the docker command to deploy Rancher, pointing it toward your certificate.
|
||||
|
||||
@@ -69,12 +68,13 @@ If you elect to use a self-signed certificate to encrypt communication, you must
|
||||
While running the Docker command to deploy Rancher, point Docker toward your CA certificate file.
|
||||
|
||||
```
|
||||
docker run -d -p 80:80 -p 443:443 \
|
||||
docker run -d --restart=unless-stopped \
|
||||
-p 80:80 -p 443:443 \
|
||||
-v /etc/your_certificate_directory/cacerts.pem:/etc/rancher/ssl/cacerts.pem \
|
||||
rancher/rancher
|
||||
rancher/rancher:latest
|
||||
```
|
||||
|
||||
### Option B—Bring Your Own Certificate: Signed by Recognized CA
|
||||
### Option B-Bring Your Own Certificate: Signed by Recognized CA
|
||||
|
||||
If your cluster is public facing, it's best to use a certificate signed by a recognized CA.
|
||||
|
||||
@@ -89,10 +89,12 @@ If your cluster is public facing, it's best to use a certificate signed by a rec
|
||||
If you use a certificate signed by a recognized CA, installing your certificate in the Rancher container isn't necessary. Just run the basic install command below.
|
||||
|
||||
```
|
||||
docker run -d -p 80:80 -p 443:443 rancher/rancher
|
||||
docker run -d --restart=unless-stopped \
|
||||
-p 80:80 -p 443:443 \
|
||||
rancher/rancher:latest
|
||||
```
|
||||
|
||||
## Part 3—Configure Load Balancer
|
||||
## Part 3-Configure Load Balancer
|
||||
|
||||
When using a load balancer in front of your Rancher container, there's no need for the container to redirect port communication from port 80 or port 443. By passing the header `X-Forwarded-Proto:
|
||||
https` header, this redirect is disabled.
|
||||
@@ -151,11 +153,11 @@ server {
|
||||
}
|
||||
```
|
||||
|
||||
<!-- #### Example HAProxy configuration
|
||||
## Part 4-Remove Default Certificates
|
||||
|
||||
#### Example Amazon ELB configuration -->
|
||||
**For those using a certificate signed by a recognized CA:**
|
||||
|
||||
## Part 4—Remove Default Certificates
|
||||
>**Note:** If you're using a self-signed certificate, you don't have to complete this part.
|
||||
|
||||
By default, Rancher automatically generates self-signed certificates for itself after installation. However, since you've provided your own certificates, you must disable the certificates that Rancher generated for itself.
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ Installation of Rancher on a single node involves multiple procedures. Review th
|
||||
|
||||
Choose an SSL option for Rancher communication encryption. After choosing an option, run the command that accompanies it to deploy Rancher.
|
||||
|
||||
## Part 1—Provision Linux Host
|
||||
## Part 1-Provision Linux Host
|
||||
|
||||
Provision a single Linux host to launch your {{< product >}} Server.
|
||||
|
||||
@@ -33,18 +33,18 @@ Provision a single Linux host to launch your {{< product >}} Server.
|
||||
|
||||
{{< note_server-tags >}}
|
||||
|
||||
## Part 2—Choose an SSL Option and Install Rancher
|
||||
## Part 2-Choose an SSL Option and Install Rancher
|
||||
|
||||
For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster.
|
||||
|
||||
Choose from the following options:
|
||||
|
||||
- [Option A—Default Self-Signed Certificate](#option-a-default-self-signed-certificate)
|
||||
- [Option B—Bring Your Own Certificate: Self-Signed](#option-b-bring-your-own-certificate-self-signed)
|
||||
- [Option C—Bring Your Own Certificate: Signed by Recognized CA](#option-c-bring-your-own-certificate-signed-by-recognized-ca)
|
||||
- [Option D—Let's Encrypt Certificates](#option-d-lets-encrypt-certificates)
|
||||
- [Option A-Default Self-Signed Certificate](#option-a-default-self-signed-certificate)
|
||||
- [Option B-Bring Your Own Certificate: Self-Signed](#option-b-bring-your-own-certificate-self-signed)
|
||||
- [Option C-Bring Your Own Certificate: Signed by Recognized CA](#option-c-bring-your-own-certificate-signed-by-recognized-ca)
|
||||
- [Option D-Let's Encrypt Certificates](#option-d-let-s-encrypt-certificate)
|
||||
|
||||
### Option A—Default Self-Signed Certificate
|
||||
### Option A-Default Self-Signed Certificate
|
||||
|
||||
If you install Rancher without specifying your own certificate, Rancher generates a self-signed certificate that's used for encryption. If you're satisfied with this certificate, there's no need to obtain your own.
|
||||
|
||||
@@ -52,11 +52,13 @@ If you install Rancher without specifying your own certificate, Rancher generate
|
||||
|
||||
1. From your Linux host, run the Docker command to install Rancher without any additional parameters:
|
||||
|
||||
```
|
||||
docker run -d -p 80:80 -p 443:443 rancher/rancher
|
||||
```
|
||||
```
|
||||
docker run -d --restart=unless-stopped \
|
||||
-p 80:80 -p 443:443 \
|
||||
rancher/rancher:latest
|
||||
```
|
||||
|
||||
### Option B—Bring Your Own Certificate: Self-Signed
|
||||
### Option B-Bring Your Own Certificate: Self-Signed
|
||||
|
||||
Your Rancher install can use a self-signed certificate that you provide to encrypt communications.
|
||||
|
||||
@@ -74,15 +76,16 @@ Your Rancher install can use a self-signed certificate that you provide to encry
|
||||
|
||||
1. After creating your certificate, run the Docker command to install Rancher, pointing toward your certificate files.
|
||||
|
||||
```
|
||||
docker run -d -p 80:80 -p 443:443 \
|
||||
```
|
||||
docker run -d --restart=unless-stopped \
|
||||
-p 80:80 -p 443:443 \
|
||||
-v /etc/<CERT_DIRECTORY>/fullchain.pem:/etc/rancher/ssl/cert.pem \
|
||||
-v /etc/<CERT_DIRECTORY>/privkey.pem:/etc/rancher/ssl/key.pem \
|
||||
-v /etc/<CERT_DIRECTORY>/cacerts.pem:/etc/rancher/ssl/cacerts.pem \
|
||||
rancher/rancher
|
||||
```
|
||||
rancher/rancher:latest
|
||||
```
|
||||
|
||||
### Option C—Bring Your Own Certificate: Signed by Recognized CA
|
||||
### Option C-Bring Your Own Certificate: Signed by Recognized CA
|
||||
|
||||
If you're publishing your app publically, you should ideally be using a certificate signed by a recognized CA.
|
||||
|
||||
@@ -99,19 +102,21 @@ If you're publishing your app publically, you should ideally be using a certific
|
||||
|
||||
After obtaining your certificate, run the Docker command to deploy Rancher, pointing toward your certificate files.
|
||||
|
||||
```
|
||||
docker run -d -p 80:80 -p 443:443 \
|
||||
-v /etc/your_certificate_directory/fullchain.pem:/etc/rancher/ssl/cert.pem \
|
||||
-v /etc/your_certificate_directory/privkey.pem:/etc/rancher/ssl/key.pem \
|
||||
rancher/rancher
|
||||
```
|
||||
```
|
||||
docker run -d --restart=unless-stopped \
|
||||
-p 80:80 -p 443:443 \
|
||||
-v /etc/your_certificate_directory/fullchain.pem:/etc/rancher/ssl/cert.pem \
|
||||
-v /etc/your_certificate_directory/privkey.pem:/etc/rancher/ssl/key.pem \
|
||||
rancher/rancher:latest
|
||||
```
|
||||
|
||||
### Option D—Let's Encrypt Certificate
|
||||
### Option D-Let's Encrypt Certificate
|
||||
|
||||
Rancher supports Let's Encrypt certificates. Let's Encrypt uses an http-01 challenge to verify that you have control over your domain. You can confirm that you control the domain by pointing the hostname that you want to use for Rancher access (for example, `rancher.mydomain.com`) to the IP of the machine it is running on. You can bind the hostname to the IP address by creating an A record in DNS.
|
||||
|
||||
>**Prerequisites:**
|
||||
>
|
||||
>- Let's Encrypt is an internet service, this cannot be used out of the box on an internal/airgapped network.
|
||||
>- Create a record in your DNS that binds your Linux host IP address to the hostname that you want to use for Rancher access (`rancher.mydomain.com` for example).
|
||||
>- Open port `TCP/80` on your Linux host. The Let's Encrypt http-01 challenge can come from any source IP address, so port `TCP/80` must be open to all IP addresses.
|
||||
|
||||
@@ -120,19 +125,16 @@ Rancher supports Let's Encrypt certificates. Let's Encrypt uses an http-01 chall
|
||||
|
||||
Run the following commands from your Linux host.
|
||||
|
||||
1. Obtain your certificate.
|
||||
1. Run the Docker command
|
||||
|
||||
```
|
||||
docker run -d -p 80:80 -p 443:443 rancher/rancher --acme-domain rancher.mydomain.com
|
||||
```
|
||||
```
|
||||
docker run -d --restart=unless-stopped \
|
||||
-p 80:80 -p 443:443 \
|
||||
rancher/rancher:latest \
|
||||
--acme-domain rancher.mydomain.com
|
||||
```
|
||||
|
||||
>**Remember:** Let's Encrypt provides rate limits for requesting new certificates. Therefore, limit how often you create or destroy the container. For more information, see [Let's Encrypt documentation on rate limits](https://letsencrypt.org/docs/rate-limits/).
|
||||
|
||||
2. Install Rancher
|
||||
|
||||
```
|
||||
$ sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher:latest
|
||||
```
|
||||
>**Remember:** Let's Encrypt provides rate limits for requesting new certificates. Therefore, limit how often you create or destroy the container. For more information, see [Let's Encrypt documentation on rate limits](https://letsencrypt.org/docs/rate-limits/).
|
||||
|
||||
## SSL FAQ / Troubleshooting
|
||||
|
||||
|
||||
@@ -4,8 +4,9 @@
|
||||
<p><b>Command</b></p>
|
||||
|
||||
<pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4">
|
||||
docker run -d -p 80:80 -p 443:443 \
|
||||
-v /host/rancher:/var/lib/rancher \
|
||||
rancher/rancher
|
||||
</pre>
|
||||
docker run -d --restart=unless-stopped \
|
||||
-p 80:80 -p 443:443 \
|
||||
-v /host/rancher:/var/lib/rancher \
|
||||
rancher/rancher:latest
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user