The binary can be downloaded directly from the UI. The link can be found in the right hand side of the footer in the UI. We have binaries for Windows, Mac, and Linux. You can also check the releases page for our CLI for direct downloads of the binary.
There are several methods you can configure the settings that the Rancher CLI uses when interacting with Rancher, i.e. Rancher URL and account API keys. Account API keys can be created in API.
There is a specific load order for what will be used.
rancher config, you’ll set the Rancher URL and API keys. If there are multiple environments, then you will select a specific environment.
You can run
rancher config to set up your configuration with Rancher server.
$ rancher config URL : http://<server_ip>:8080 Access Key : <accessKey_of_account_api_key> Secret Key : <secretKey_of_account_api_key> # If there are more than one environment, # you will be asked to select which environment to work with Environments:  Default(1a5)  k8s(1a10) Select: 1 INFO Saving config to /Users/<username>/.rancher/cli.json
You can set the following environment variables,
# Set the url that Rancher is on $ export RANCHER_URL=http://<server_ip>:8080 # Set the access key, i.e. username $ export RANCHER_ACCESS_KEY=<accessKey_of_account_api_key> # Set the secret key, i.e. password $ export RANCHER_SECRET_KEY=<secretKey_of_account_api_key>
If there is more than one environment in your Rancher server you’ll also need to set an environment variable to select the specific environment, i.e.
# Set the environment to use, you can use either environment ID or environment name $ export RANCHER_ENVIRONMENT=<environment_id>
If you choose not to run
rancher config or set environment variables, you can pass the same values as options as part of any
$ rancher --url http://server_ip:8080 --access-key <accessKey_of_account_api_key> --secret-key <secretKey_of_account_api_key> --env <environment_id> ps
When working with Rancher CLI, you can set the environment variable,
true, which will have all CLI commands print out verbose messages of the API calls being made.
# Print verbose messages for all CLI calls $ export RANCHER_CLIENT_DEBUG=true
If you don’t want the verbose response on every CLI command, set the environment variable
false and pass in
--debug to the specific command to get the verbose messages.
$ rancher --debug env create newEnv
If you use an account API key, you will be able to create and update environments. If you use an environment API key, you will not be able to create or update other environments and you will only be able to see your existing environment.
$ rancher env ls ID NAME STATE CATALOG SYSTEM DETAIL 1e1 zookeeper healthy catalog://community:zookeeper:1 false 1e2 Default healthy false 1e3 App1 healthy false
There are some commands (e.g.
rancher docker and
rancher ssh) that require selecting a specific host to use. You can either set up an environment variable to select a host, i.e.
RANCHER_DOCKER_HOST, or pass in the ` –host` to specify a host.
Before selecting a host, you can list out all the hosts in the environment.
$ rancher hosts ID HOSTNAME STATE IP 1h1 host-1 active 111.222.333.444 1h2 host-3 active 111.222.333.445 1h3 host-2 active 111.222.333.446
Now, you can set the environment variable,
RANCHER_DOCKER_HOST, or pass in
--host using either the host ID or host name to select a different host.
# Set the host to always select host-1 (1h1) $ export RANCHER_DOCKER_HOST=1h1 # List the containers running on host-1 $ rancher docker ps # List the containers running on host-2 $ rancher --host host-2 docker ps
In your selected environment, you can view all the services running in an environment.
$ rancher ps ID TYPE NAME IMAGE STATE SCALE ENDPOINTS DETAIL 1s1 service zookeeper/zk rawmind/alpine-zk:3.4.8-4 healthy 3 1s2 service Default/nginxApp nginx healthy 1 1s4 service App1/db1 mysql healthy 1 1s5 service App1/wordpress wordpress healthy 4 1s6 loadBalancerService App1/wordpress-lb healthy 1 111.222.333.444:80
Instead of specific services, you can view all the containers in the environment.
$ rancher ps -c ID NAME IMAGE STATE HOST IP DOCKER DETAIL 1i1 zookeeper_zk_zk-volume_1 rawmind/alpine-volume:0.0.1-1 stopped 1h1 a92b6d3dad18 1i2 zookeeper_zk_zk-conf_1 rawmind/rancher-zk:0.3.3 stopped 1h1 2e8085a4b517 1i3 zookeeper_zk_1 rawmind/alpine-zk:3.4.8-4 healthy 1h1 10.42.150.2 e3ef1c6ff70e 1i5 zookeeper_zk_zk-volume_2 rawmind/alpine-volume:0.0.1-1 stopped 1h2 e716f562e0a4 1i6 zookeeper_zk_zk-conf_2 rawmind/rancher-zk:0.3.3 stopped 1h2 5cd1cebea5a3 1i7 zookeeper_zk_2 rawmind/alpine-zk:3.4.8-4 healthy 1h2 10.42.88.102 21984a4445d1 1i9 zookeeper_zk_zk-volume_3 rawmind/alpine-volume:0.0.1-1 stopped 1h3 7c614003f08c 1i10 zookeeper_zk_zk-conf_3 rawmind/rancher-zk:0.3.3 stopped 1h3 53fb77cd8ae0 1i11 zookeeper_zk_3 rawmind/alpine-zk:3.4.8-4 healthy 1h3 10.42.249.162 84a80eb8e037 1i13 Default_nginxApp_1 nginx running 1h1 10.42.107.28 e1195a563280 1i15 App1_db1_1 mysql running 1h3 10.42.116.171 0624e0a7f2fc 1i16 App1_wordpress_1 wordpress running 1h1 10.42.66.199 4bb77abebc08 1i17 App1_wordpress-lb_1 rancher/lb-service-haproxy:v0.4.2 healthy 1h2 10.42.199.163 5d3a005278d3 1i18 App1_wordpress_2 wordpress running 1h2 10.42.88.114 01ec967c49ac 1i19 App1_wordpress_3 wordpress running 1h3 10.42.218.81 3aae3fc6163a 1i20 App1_wordpress_4 wordpress running 1h1 10.42.202.31 0b67ef86db22
If you wanted to view the containers of a specific service, you can list out all the containers running in a service by adding in the service ID or service name.
$ rancher ps 1s5 ID NAME IMAGE STATE HOST IP DOCKER DETAIL 1i16 App1_wordpress_1 wordpress running 1h1 10.42.66.199 4bb77abebc08 1i18 App1_wordpress_2 wordpress running 1h2 10.42.88.114 01ec967c49ac 1i19 App1_wordpress_3 wordpress running 1h3 10.42.218.81 3aae3fc6163a 1i20 App1_wordpress_4 wordpress running 1h1 10.42.202.31 0b67ef86db22
To start adding services into Rancher, you can create a simple
docker-compose.yml file and optionally a
rancher-compose.yml file. If there is no
rancher-compose.yml file, then all services will start with a scale of 1 container.
version: '2' services: service1: image: nginx
version: '2' services: # Reference the service that you want to extend service1: scale: 2
After your files are created, you can launch the services into Rancher server.
# Creating and starting a service without environment variables and selecting a stack # If no stack is provided, the stack name will be the folder name that the command is running from # If the stack does not exist in Rancher, it will be created # Add in -d at the end to not block and log $ rancher --url URL_of_Rancher --access-key <username_of_account_api_key> --secret-key <password_of_account_api_key> --env Default up -s stack1 -d # Creating and starting a service with environment variables already set # Add in -d at the end to not block and log $ rancher up -s stack1 -d # To change the scale of an existing service, you can use stackName/serviceName or service ID $ rancher scale Default/service1=3 $ rancher scale 1s4=5
If you have been using the Docker CLI to add in services, you can also add containers into Rancher using
# Services should be stackName/service_name $ rancher run --name stackA/service1 nginx
To read more about all the supported commands, please read our rancher command documentation.