Improve docker image setup #43

New issue

Closed

opened 2022-01-20 09:18:11 +01:00 by Jef Roosens · 1 comment

Jef Roosens commented

2022-01-20 09:18:11 +01:00

Owner

We want to release two types of Docker image, namely a dynamically linked Alpine-based one & a statically linked "bare" image. Both these images should contain the following things:

Healthcheck
Anonymous volume on data directory?
Don't run as root
dumb-init as init

Specifically for the "bare" image, there also:

Build images in CI from build artifacts

This one needs some clarification. During our CI testing, we build statically compiled production images on all three supported platforms. This means that, instead of rebuilding these, we could run these builds again when merging into dev & upload them to a commit-specific directory in a CI bucket. Afterwards, we can let the agent builder the actual image pull the relevant binary from this bucket, greatly speeding up the buildx process.

We want to release two types of Docker image, namely a dynamically linked Alpine-based one & a statically linked "bare" image. Both these images should contain the following things: - [x] Healthcheck - [ ] Anonymous volume on data directory? - [x] Don't run as root - [x] dumb-init as init Specifically for the "bare" image, there also: - [x] Build images in CI from build artifacts This one needs some clarification. During our CI testing, we build statically compiled production images on all three supported platforms. This means that, instead of rebuilding these, we could run these builds again when merging into dev & upload them to a commit-specific directory in a CI bucket. Afterwards, we can let the agent builder the actual image pull the relevant binary from this bucket, greatly speeding up the buildx process.