From 0e088dd68c0c9d20984d22fc1bca9d33588da703 Mon Sep 17 00:00:00 2001 From: Ivan Mikushin Date: Mon, 21 Mar 2016 15:33:04 -0700 Subject: [PATCH] Created How to set up a RancherOS CI on an ARM (ARM64) docker host (markdown) --- ...ancherOS-CI-on-an-ARM-(ARM64)-docker-host.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 How-to-set-up-a-RancherOS-CI-on-an-ARM-(ARM64)-docker-host.md diff --git a/How-to-set-up-a-RancherOS-CI-on-an-ARM-(ARM64)-docker-host.md b/How-to-set-up-a-RancherOS-CI-on-an-ARM-(ARM64)-docker-host.md new file mode 100644 index 0000000..f9db78d --- /dev/null +++ b/How-to-set-up-a-RancherOS-CI-on-an-ARM-(ARM64)-docker-host.md @@ -0,0 +1,17 @@ +# Drone CI Setup Instructions for ARM/ARM64 + +These are almost exactly the same as [for the regular Drone CI](https://github.com/rancher/os/wiki/How-to-set-up-RancherOS-CI), with only a couple differences: + +## 1. Drone CI server docker image + +Use `armhfbuild/drone:0.4` as the Drone CI server image. Should run fine on ARM (like Raspberry Pi 2) and ARM64 (like Estuary D02) docker hosts. + +## 2. arm/arm64 rancher/dapper image + +Make sure you've done the following before having Drone run RancherOS builds. Run against the same docker daemon you're running Drone with: +``` +docker pull rancher/dapper:1.10.3_arm +docker tag rancher/dapper:1.10.3_arm rancher/dapper:1.10.3 +``` + +This is necessary because `.drone.yml` syntax does not support choosing the image based on the host platform. The actual `rancher/dapper:1.10.3` image on DockerHub is for amd64 (x86_64), so your builds won't run if you don't do that.