CoreOS Container Linux Logo

A container-focused OS that's designed for painless management in large clusters

Running CoreOS Container Linux on Brightbox Cloud

These instructions will walk you through running a Container Linux cluster on Brightbox. This guide uses the Brightbox CLI but you can also use the Brightbox Manager.

Firewall policy

First of all, let’s create a server group to put the new servers into:

$ brightbox groups create -n "coreos"

Creating a new server group

 id         server_count  name  
 grp-cdl6h  0             coreos

And then create a firewall policy for the group using its identifier:

$ brightbox firewall-policies create -n "coreos" grp-cdl6h

 id         server_group  name  
 fwp-dw0n6  grp-cdl6h     coreos

Firewall rules

Now let’s define the firewall rules for this new policy. First we’ll allow ssh access in from anywhere:

$ brightbox firewall-rules create --source any --protocol tcp --dport 22 fwp-dw0n6

 id         protocol  source  sport  destination  dport  icmp_type  description
 fwr-i513z  tcp       any     -      -            22     -                     

And then we’ll allow the etcd ports 7001 and 4001, allowing access from only the other nodes in the group.

$ brightbox firewall-rules create --source grp-cdl6h --protocol tcp --dport 7001,4001 fwp-dw0n6

 id         protocol  source     sport  destination  dport      icmp_type  description
 fwr-xax48  tcp       grp-cdl6h  -      -            7001,4001  -                     

And then allow all outgoing access from the servers in the group:

$ brightbox firewall-rules create --destination any fwp-dw0n6

 id         protocol  source  sport  destination  dport  icmp_type  description
 fwr-dtzim  -         -       -      any          -      -                     

List images

You can find it by listing all images and grepping for CoreOS:

$ brightbox images list | grep CoreOS

 id         owner      type      created_on  status   size   name
   brightbox  official  2013-12-15  public   5442   CoreOS  (x86_64)


Container Linux allows you to configure machine parameters, launch systemd units on startup and more via cloud-config. We're going to provide the cloud-config data via the user-data-file flag.

A sample common cloud-config file will look something like the following:


    # generate a new token for each unique cluster from
    # specify the initial size of your cluster with ?size=X
    # multi-region and multi-cloud deployments need to use $public_ipv4
    advertise-client-urls: http://$private_ipv4:2379,http://$private_ipv4:4001
    initial-advertise-peer-urls: http://$private_ipv4:2380
    # listen on both the official ports and the legacy ports
    # legacy ports can be omitted if your application doesn't depend on them
    listen-peer-urls: http://$private_ipv4:2380
    - name: etcd2.service
      command: start
    - name: fleet.service
      command: start
CoreOS cloud-configs can validated using the online validator.

The $private_ipv4 and $public_ipv4 substitution variables are fully supported in cloud-config on Brightbox.

Building servers

Now build three servers using the image, in the server group we created and specifying the cloud-config as the user data:

$ brightbox servers create -i 3 --type small --name "coreos" --user-data-file ./user-data --server-groups grp-cdl6h 

Creating 3 small (typ-8fych) servers with image CoreOS  () in groups grp-cdl6h with 0.05k of user data

 id         status    type   zone   created_on  image_id   cloud_ip_ids  name  
 srv-ko2sk  creating  small  gb1-a  2013-10-18                  coreos
 srv-vynng  creating  small  gb1-a  2013-10-18                  coreos
 srv-7tf5d  creating  small  gb1-a  2013-10-18                  coreos

Accessing the cluster

Those servers should take just a minute to build and boot. They automatically install your Brightbox Cloud ssh key on bootup, so you can ssh in straight away as the core user.

If you’ve got ipv6 locally, you can ssh in directly:

$ ssh
The authenticity of host ' (2a02:1348:17c:423d:24:19ff:fef1:8f6)' can't be established.
RSA key fingerprint is 99:a5:13:60:07:5d:ac:eb:4b:f2:cb:c9:b2:ab:d7:21.
Are you sure you want to continue connecting (yes/no)? yes

Last login: Thu Oct 17 11:42:04 UTC 2013 from on pts/0
   ______                ____  _____
  / ____/___  ________  / __ \/ ___/
 / /   / __ \/ ___/ _ \/ / / /\__ \
/ /___/ /_/ / /  /  __/ /_/ /___/ /
\____/\____/_/   \___/\____//____/
core@srv-n8uak ~ $

If you don’t have ipv6, you’ll need to create and map a Cloud IP first.

Using CoreOS Container Linux

Now that you have a cluster bootstrapped it is time to play around. Check out the Container Linux Quickstart guide or dig into more specific topics.