Run concourse workers using ARM devices (yep, including your Raspberry Pi!)

• what's inside?
• how does it work?
• installing
  • using docker
  • binaries
• building from source
  • dependencies
  • steps
• todo
• license

A slightly modified version of Concourse, having just a single resource type (registry-image).

For some info on what was needed for Concourse to run on ARM, check out the "How does it work?" doc.

concourse-arm is provided in two flavors:

• container images (see "using docker"), and
• raw binaries (see "binaries")

Images are published with the platform already set according to the platform.

docker pull cirocosta/concourse-arm:5.2.0

If you need/want to be more explicit, there are also tagged versions:

docker pull cirocosta/concourse-arm:5.2.0-armhf
docker pull cirocosta/concourse-arm:5.2.0-arm64

With the image present, the standard Docker configurations that you can find under concourse/concourse-docker apply.

The tl;dr for having a single worker that has the right keys under /tmp/keys:

docker run \
		--detach \
		--privileged \
		--stop-signal=SIGUSR2 \
		--volume /tmp/keys:/concourse-keys:ro \
		cirocosta/concourse-arm:5.2.0-arm64 \
		worker \
		--name=arm64 \
		--tag=arm \
		--tsa-host=hush-house.pivotal.io:2222

Just like you'd install the regular AMD64 version of Concourse, all that's needed is placing the contents of the gzipped tarball into /usr/local:

tar -zxvf concourse-*.tgz -C /usr/local

• v5.2.0 armhf
• v5.2.0 arm64

All of the source code necessary for building concourse-arm is packed in the this repository by leveraging git submodules.

component	build status
builder
registry-image
concourse

Regardless of the desired output (container images or binaries), the process of building the components require something that can build Dockerfiles (either Docker itself or other builders like buildkit, img or anything like that).

The only hard requirement is that when building targets that require running steps that execute ARM-based binaries, the ability to run those is essential (Docker for Mac makes that super easy, but a combination of binfmt_misc and qemu-user-static also works).

1. clone this repo with all submodules

git clone https://github.com/cirocosta/concourse-arm --recurse-submodules -j2

2. build the cirocosta/concourse-arm:(arm64|armhf) container images

make images -j4

If everything went all right, this is what you'll end up with:

build
├── arm64
│   ├── concourse
│   │   ├── bin
│   │   │   ├── concourse
│   │   │   ├── fly
│   │   │   ├── gdn
│   │   │   ├── gdn-dadoo
│   │   │   ├── gdn-init
│   │   │   └── runc
│   │   └── resource-types
│   │       └── registry-image
│   │           ├── resource_metadata.json
│   │           └── rootfs.tgz
│   └── concourse.tgz
└── armhf
    ├── concourse
    │   ├── bin
    │   │   ├── concourse
    │   │   ├── fly
    │   │   ├── gdn
    │   │   ├── gdn-dadoo
    │   │   ├── gdn-init
    │   │   └── runc
    │   └── resource-types
    │       └── registry-image
    │           ├── resource_metadata.json
    │           └── rootfs.tgz
    └── concourse.tgz

ps.: building the container images will involve generating binaries and resource types under ./build for each supported architecture.

There are few things that still need to be finished:

• have runc running with seccomp enabled

See the LICENSE file.