Wednesday, 29 November 2017

IBM Cloud Private - My personal success ...

I've spent much of the past few days attempting to get IBM Cloud Private (ICP) 2.1.0 deployed onto my own set of Linux VMs.

This follows on from an internal enablement session last week, where I was able to get ICP up and running without huge problems.

So this time around, I created three VMs ( one for the boot/master/management node, one for a worker node and one for the proxy node ), which is probably a minimally viable configuration ( one would typically have 2-3 worker nodes, for scalability ).

I downloaded the latest Ubuntu Linux ( 17.10 aka Artful ), and then installed the latest version of Docker CE17.11.0-ce ).

Having followed the installation guide ( well, an edited version from the enablement ), I was disappointed to find that the installation failed with: -


At the suggestion of a friend, I checked my /etc/hosts file: -


and the ICP cluster hosts file: -


I'd previously ensured that I had sufficient disk ( 150 GB per VM ) and RAM ( 8 GB per VM ).

Overnight, I had an inspiration … and checked the System Requirements pages: -



Note that Ubuntu 17.10 is NOT listed.


For all supported operating systems, Docker Enterprise Edition and Docker Community Edition versions 1.12 to 1.13.1 are supported. Docker Community Edition versions 17.03, 17.05, and 17.06 and Docker Enterprise Edition version 17.03 are also supported.

Note that Docker 17.11 is NOT listed.

Once I switched to supported versions of Ubuntu: -

lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial


and a lower version of Docker: -

docker version

Client:
 Version:      17.09.0-ce
 API version:  1.32
 Go version:   go1.8.3
 Git commit:   afdb6d4
 Built:        Tue Sep 26 22:42:18 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.09.0-ce
 API version:  1.32 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   afdb6d4
 Built:        Tue Sep 26 22:40:56 2017
 OS/Arch:      linux/amd64
 Experimental: false


things just worked: -


No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...