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

Comments

Popular posts from this blog

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 and Advise which change the object returned by the method in the step 2:
... @Named @Aspect public class Dyn…

Smart Home Sweet Home with Gigaset Elements?

Introduction
Last week I had a chance to try the Smart Home solution from Gigaset Elements. I read some articles about this product which said how easy to install this product for dummy users. Those articles woke my interest and I began to google products for Smart Home solutions.

In this article (German language) you will find a nice overview about some products for Smart Home, which can be bought in Germany. The Nest product from Google is still not available in Germany. Although it seems that RWE will offer Nest products in Germany in couple of months.

The installation of Gigaset Elements was really easy. The problem I encountered was to add the sirensensor. I had to push hard the button on the siren sensor at the same time with the button on the base, so that they can communicate with each other. After about one hour I managed to install everything properly.

Points to mention
Generally the idea is very nice. Gigaset Elements try to push KISS (Keep it Simple Stupid) principle. Howev…

GWT Training for Java Developers with GWT Boot

I'm always a fan of "one language solution with Java to rule them all", here are sofar my opinions about Polyglot Programming:
Why "Polyglot Programming" or "Do It Yourself Programming Languages" or "Language Oriented Programming" sucks?Warum Polyglot Programming nicht praxistauglich istJava als universelle Programmiersprache Until today nobody can excite me about Polyglot Programming. My points are getting another big support after I read the "Rise of Polyglot at Netflix" presentation which says that Polyglot is expensive, also for company in the category of Netflix. At the end of the day we need to be productive. Our applications should have a high quality standard and the total costs (TCO) of our software development should be manageable and low. To be able to reach this goal we have Java with Spring Boot or JakartaEE on the server-side which offers REST interfaces. So logically for user interface development on the client-side I…