Une gomme.

Getting started with Docker on Online Labs C1

Manfred Touron - @moul Sébastien Rannou - @aimxhaisse

• Dedicated ARM servers • Run in the Cloud • Ultra high-density (912 servers per rack) • Developed / Made / Running in France

What is Online Labs’ C1 ?

4 true cores

ARMv7 CPU

2GB of RAM

1 Gbit/s network link

SSD storage

C1 Server

1 x C1 node

• 4-cores

• 2Gb memory

• 1Gbps Ethernet

• SSD disk over network

=19 x C1 nodes

• 18 compute nodes

• 1 SAN node + 6 disks

• 1 managed switch

• 10gbps connectivity

• serial multiplexer

1 x C1 blade 76 cores 38G ram

• 16 blades per chassis

• 3 chassis per rack

• “hot-plug”

• > 2000 leds :)

• 33ºC

= 912 x C1 nodes

3.6k cores 1.8T ram 288 disks

= 48 x C1 blades= 3 x C1 chassis

1 x C1 rack

Mainline Linux v3.17 kernel

armel/armhf linux distributions

Ubuntu (from 14.04) - Fedora 20 - Debian 7 - Gentoo

InstantApps: Docker, Wordpress, Pydio, Owncloud, Ghost

What runs on C1

• All features supported • Storage drivers: AUFS, BTRFS, DeviceMapper • cgroups, volumes, ports, links

• fig, nsenter, gosu and pipework are installed by default

Docker + C1

We ported the distrib images to armhf The registry doesn’t care about the architecture

Prefixing all our images (armbuild/)

Docker image -> single architecture

FROM ubuntu:trusty Becomes

FROM armbuild/ubuntu:trusty

Porting a Docker image

github.com/moul/port-docker-image

Distribs: ubuntu, debian, fedora, busybox Langs: go, ruby, python, …

Apps: redis, rabbitmq, mysql, … (> 100 ported images)

Ported images

registry.hub.docker.com/armbuild - github.com/armbuild

Port more distribution images: centos, archlinux

Work on trusted builds for ARM images (partial support)

Port a Docker-based PAAS (dokku, flynn, mesos, coreos …)

Work on multi-architecture / cross-platform images

What we are working on

registry.hub.docker.com/armbuild - github.com/armbuild

Joyeux Noël

……………….