Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/cirocosta/concourse-arm
Concourse on ARMv7 and Arm64
https://github.com/cirocosta/concourse-arm
arm concourse continuous-integration raspberry-pi
Last synced: 2 months ago
JSON representation
Concourse on ARMv7 and Arm64
- Host: GitHub
- URL: https://github.com/cirocosta/concourse-arm
- Owner: cirocosta
- License: apache-2.0
- Created: 2019-04-20T19:21:05.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2019-06-01T12:46:51.000Z (over 5 years ago)
- Last Synced: 2024-10-04T20:30:55.063Z (3 months ago)
- Topics: arm, concourse, continuous-integration, raspberry-pi
- Language: Dockerfile
- Homepage:
- Size: 43 KB
- Stars: 5
- Watchers: 2
- Forks: 6
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# concourse-arm
Run [`concourse`](https://concourse-ci.org) workers using ARM devices (yep, including your Raspberry Pi!)
- [what's inside?](#whats-inside)
- [how does it work?](#how-does-it-work)
- [installing](#installing)
- [using docker](#using-docker)
- [binaries](#binaries)
- [building from source](#building-from-source)
- [dependencies](#dependencies)
- [steps](#steps)
- [todo](#todo)
- [license](#license)
## what's inside?
A slightly modified version of Concourse, having just a single resource type ([`registry-image`](https://github.com/concourse/registry-image-resource)).
## how does it work?
For some info on what was needed for Concourse to run on ARM, check out the ["How does it work?"](./docs/how-does-it-work.md) doc.
## installing
`concourse-arm` is provided in two flavors:
- container images (see ["using docker"](#using-docker)), and
- raw binaries (see ["binaries"](#binaries))
### using docker
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`](https://github.com/concourse/concourse-docker) apply.
The tl;dr for having a single worker that has the right keys under `/tmp/keys`:
```sh
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
```
### binaries
Just like you'd [install the regular AMD64 version of Concourse](https://concourse-ci.org/install.html#install), 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](https://github.com/cirocosta/concourse-arm/releases/download/v5.2.0/concourse-armhf.tgz)
- [v5.2.0 arm64](https://github.com/cirocosta/concourse-arm/releases/download/v5.2.0/concourse-arm64.tgz)
## building from source
All of the source code necessary for building `concourse-arm` is packed in the this repository by leveraging [git submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules).
| component | build status |
| -------------- | ------------ |
| builder |  |
| registry-image |  |
| concourse |  |
### dependencies
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](https://github.com/moby/buildkit), [img](https://github.com/genuinetools/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](https://docs.docker.com/docker-for-mac/install/) makes that super easy, but a combination of `binfmt_misc` and `qemu-user-static` also works).
### steps
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.
## todo
There are few things that still need to be finished:
- [ ] have `runc` running with seccomp enabled
## license
See [the LICENSE file](./LICENSE).