Skip to main content

Rancher 1.6 on Macbook

Introduction

Installing Rancher 1.6 on your Macbook should be straight forward. In my case it was not as easy as I thought because of version compatibility between Docker and Rancher. Here are my steps, enjoy.

Install Docker Toolbox in your Macbook

First of all Rancher 1.6 does not support Docker for Mac, so instead you need Docker Toolbox for Mac. Check this page for differences between Docker for Mac and Docker Toolbox for Mac.
One important point at the time you install Docker Toolbox for Mac: you need to get the correct version of the supported Docker. Rancher 1.6 supports some Docker versions. You can check the list on this support page. If you are trying for the first time please get the Community Edition (ce) of Docker. Here is a functional example:
  • Docker Toolbox for Mac Version 17.06.0-ce. Download: https://github.com/docker/toolbox/releases/tag/v17.06.0-ce
  • Get the .pkg file for Macbook
  • Be careful: Docker Toolbox always downloads the current Docker version from Internet, so you won't get the version you need / want to install! Simple solution: turn off you WiFi so you can't reach Internet. After that Docker Toolbox will just use the correct local version as you downloaded it.
After the installation of Docker Toolbox for Mac can run Docker Terminal from Toolbox. Try "docker version" and you get something like this:
Be sure that you have the correct Docker version, which is supported by Rancher 1.6. and both client and server version should be identical. After this you can follow the installation steps from Rancher site. Last tip: if it's not working with "sudo docker ..." just use "docker ...".

Enjoy,
Lofi

Labels:

Comments

Post a Comment

Popular posts from this blog

Why "Polyglot Programming" or "Do It Yourself Programming Languages" or "Language Oriented Programming" sucks?

Last year we saw the launch of a new Web programming language Dart - Structured Web Programming from Google. A very interesting approach to support web application development. Not so long after Go, Groovy, Ruby, Scala, << name your DSL here >> ; we see Dart. Is it a good thing to have at least one programming language to solve one problem? The answer is, like we already know, it depends. Some important backgrounds you should know about the multi programming language paradigm are following: 1. You can read Martin Fowler article about language oriented programming with language workbenches which enables you to write small programming languages easily. In this article I see everyone writing their small languages, everywhere. In this concept we see DSL (Domain Specific Language) as the future of our programming activities. Source: http://martinfowler.com/articles/languageWorkbench.html 2. Neal Ford talked about Polyglot Programming, combining multiple programming language...
32 comments
Read more

Software Development Macro and Micro Process

If you think that in year 2012 all companies which produce software and IT divisions in our world have already their optimized software development process, you are wrong. It seems that we - software architects, software developers or whatever your title is - still need to optimize the software development process in many software companies and IT divisions. So what do you do if you enter a software company or IT division and you see following things: 1. There is a perfect project management process to handle all those development of software but it is a pure project management without a context to software development. So basically you only take care of cost, time, budget and quality factors. In the software development you still use the old fashioned waterfall process. 2. From the tooling point of view: you have a project management planning and controlling tool but you are still in the beginning of Wiki (almost no collaboration tool) and you don't use issues tracking sy...
20 comments
Read more

Creating Spring Bean dynamically in the Runtime

In my training someone asked me whether it is possible to create an object (a Spring Bean) dynamically so you can choose which implementation you want to have  in the runtime . So at the compile time you don't know what object actually should be created yet. The application should decide what object to be created based on a property file . 1. We create an annotation so we can mark the method which should be able to create the object dynamically: ... package your.package; ... @Retention(RetentionPolicy.RUNTIME) public @interface InjectDynamicObject { } ... 2. Use the new created annotation in your method which should be able to create the object dynamically: ... @Named("customerBo") public class CustomerBoImpl implements CustomerBo { ...     @Override   @InjectDynamicObject   public Customer getDynamicCustomer() {         return this.dynamicCustomer; } ... 3. Write an aspect with Pointcut a...
10 comments
Read more