Rancher is an\u00a0open source platform<\/strong>\u00a0for running containers and building a private container service. Rancher is based on Docker, so you can run it on a dedicated box,\u00a0KVM machine<\/strong>\u00a0or even on a\u00a0LXC container<\/strong>. Rancher provides a huge library of applications which are installed within a few clicks and also supports docker images from Dockerhub.<\/p>\n As stated, Docker is required to run Rancher, so we will install it first.<\/p>\n First, remove any old Docker files, if necessary.<\/p>\n Note:<\/strong>\u00a0You may get a report that no Docker files are installed. This is safe to ignore.<\/em><\/p>\n Install required packages.<\/p>\n Add a\u00a0 Check the\u00a0available versions of Docker CE.<\/strong><\/p>\n You will see output similar to the following text.<\/p>\n You can install the latest version of\u00a0Docker CE<\/strong>\u00a0simply using the\u00a0 To specify the version of Docker CE to install, append the\u00a0 Start Docker.<\/strong><\/p>\n Verify that\u00a0Docker installed correctly.<\/strong><\/p>\n This command runs a test image in a test container to print a message, then exits. The message will be similar to the following output.<\/p>\n Now we’re are ready to install Rancher.<\/p>\n Wait a few minutes to allow the Rancher UI to boot. Then, open your favorite browser and go to port\u00a0 Be sure to replace\u00a0 Rancher doesn’t configure access control by default, so it is important to set this up immediately, otherwise the UI and API can be accessed by anyone who has your IP.<\/p>\n Hover over the\u00a0 Follow the instructions in the Rancher UI to set up whichever form of access control you prefer.<\/p>\n Everything is now installed and you can begin to\u00a0configure Rancher<\/strong>. For more in-depth information on configuring and using Rancher, visit their\u00a0official documentation<\/strong><\/span><\/a>.<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","manualknowledgebasecat":[231,242],"manual_kb_tag":[344],"_links":{"self":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/2550"}],"collection":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/comments?post=2550"}],"version-history":[{"count":1,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/2550\/revisions"}],"predecessor-version":[{"id":2551,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/2550\/revisions\/2551"}],"wp:attachment":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/media?parent=2550"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manualknowledgebasecat?post=2550"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb_tag?post=2550"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Requirements<\/strong><\/h2>\n
\n
Install Docker<\/strong><\/h2>\n
sudo yum remove docker docker-common docker-selinux docker-engine\r\n<\/code><\/pre>\nsudo yum install -y yum-utils device-mapper-persistent-data lvm2\r\n<\/code><\/pre>\nstable<\/code>\u00a0repo.<\/p>\nsudo yum-config-manager --add-repo https:\/\/download.docker.com\/linux\/centos\/docker-ce.repo\r\n<\/code><\/pre>\nyum list docker-ce --showduplicates | sort -r\r\n<\/code><\/pre>\n...\r\ndocker-ce.x86_64 17.09.1.ce-1.el7.centos docker-ce-stable\r\ndocker-ce.x86_64 17.09.0.ce-1.el7.centos docker-ce-stable\r\ndocker-ce.x86_64 17.06.2.ce-1.el7.centos docker-ce-stable\r\ndocker-ce.x86_64 17.06.1.ce-1.el7.centos docker-ce-stable\r\ndocker-ce.x86_64 17.06.0.ce-1.el7.centos docker-ce-stable\r\ndocker-ce.x86_64 17.03.2.ce-1.el7.centos docker-ce-stable\r\ndocker-ce.x86_64 17.03.1.ce-1.el7.centos docker-ce-stable\r\ndocker-ce.x86_64 17.03.0.ce-1.el7.centos docker-ce-stable\r\n...\r\n<\/code><\/pre>\nsudo yum install docker-ce<\/code>\u00a0command, but in a production environment, it is recommended that you install a specific version rather than the latest version.<\/p>\nversion-string<\/code>, (second column), of the latest stable version to the package name followed by a\u00a0“-<\/code>“<\/strong>, as shown in the following command.<\/p>\nsudo yum install docker-ce-17.09.1.ce-1.el7.centos\r\n<\/code><\/pre>\nsudo systemctl start docker\r\n<\/code><\/pre>\nsudo docker run hello-world\r\n<\/code><\/pre>\nHello from Docker!\r\nThis message shows that your installation appears to be working correctly.\r\n\r\nTo generate this message, Docker took the following steps:\r\n 1. The Docker client contacted the Docker daemon.\r\n 2. The Docker daemon pulled the \"hello-world\" image from the Docker Hub.\r\n (amd64)\r\n 3. The Docker daemon created a new container from that image which runs the\r\n executable that produces the output you are currently reading.\r\n 4. The Docker daemon streamed that output to the Docker client, which sent it\r\n to your terminal.\r\n\r\nTo try something more ambitious, you can run an Ubuntu container with:\r\n $ docker run -it ubuntu bash\r\n\r\nShare images, automate workflows, and more with a free Docker ID:\r\n https:\/\/cloud.docker.com\/\r\n\r\nFor more examples and ideas, visit:\r\n https:\/\/docs.docker.com\/engine\/userguide\/\r\n<\/code><\/pre>\nInstall Rancher<\/strong><\/h2>\n
sudo docker run -d --restart=unless-stopped -p 8080:8080 rancher\/server:stable\r\n<\/code><\/pre>\n8080<\/code>\u00a0on your server.<\/p>\nhttp:\/\/192.0.2.0:8080\r\n<\/code><\/pre>\n192.0.2.0<\/code>\u00a0with your actual server’s IP address.<\/em><\/p>\nADMIN<\/code>\u00a0tab, and click\u00a0Access Control<\/code>.<\/p>\nConclusion<\/strong><\/h2>\n