Read versions from .tool-versions when building production image #464
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gerhard
force-pushed
the
read-production-versions-from-tool-versions
branch
6 times, most recently
from
a3680d7
to
aec54bf
Compare
gerhard
force-pushed
the
read-production-versions-from-tool-versions
branch
from
aec54bf
to
775a7f0
Compare
In order to minimize bugs and differences in behaviour between dev & prod, we want to be running the same runtime dependency versions (e.g. Erlang, Elixir, Node.js & PostgreSQL) in both environments. In development, we are using https://asdf-vm.com/ to manage runtime dependencies. This means that with a single command - asdf install - everyone working with our codebase can have the same dependencies installed. Currently these are: - direnv 2.32.2 - elixir 1.14.4 - erlang 25.3.2 - golang 1.20.4 - nodejs 18.16.0 - yarn 1.22.19 - postgres 14.1 - flyctl 0.1.8 - mage 1.15.0 We used to manually edit these versions in our CI/CD pipeline. Since we are using Dagger for CI/CD, this was no big deal since our pipeline is just code. But since it is code, we could go one step further. Our pipeline could read the .tool-versions file and use that information to build the container image that gets deployed to production. That's exactly what this change does. The only runtime dependency version that does not exist in .tool-versions is the OS - Ubuntu 22.04 in production. This is a reasonable limitation that we could improve as a follow-up. What I am thinking right now is that we should NOT depend on an OS for the production container image, and instead finish the migration to Elixir (Erlang) releases + one of those sweet https://github.com/chainguard-images/images#chainguard-images, maybe https://github.com/chainguard-images/images/tree/main/images/glibc-dynamic. What we are really missing is an Elixir Chainguard image. One day... Boy scout fixes: + upgrade Erlang, Node.js & Golang to latest minor + upgrade Dagger Go SDK to latest + go mod tidy + improve Dagger pipeline grouping + run pipelines in parallel 🏎 Turbo button 🏎 + use the same PostgreSQL minor in devcontainer - same version everywhere! + upgrade flyctl version to latest + install yarn, flyctl & mage via asdf + use shorter mage commands instead of go run + test asdf on a fresh macOS 16.3 (arm64) + test asdf on Debian 11 + upgrade setup-go GitHub Action to v4 Signed-off-by: Gerhard Lazu <[email protected]>
gerhard
force-pushed
the
read-production-versions-from-tool-versions
branch
from
775a7f0
to
0571e8a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to minimize bugs and differences in behaviour between dev & prod, we want to be running the same runtime dependency versions (e.g. Erlang, Elixir, Node.js & PostgreSQL) in both environments.
In development, we are using https://asdf-vm.com/ to manage runtime dependencies. This means that with a single command -
asdf install- everyone working with our codebase can have the same dependencies installed. Currently these are:We used to manually edit these versions in our CI/CD pipeline. Since we are using Dagger for CI/CD, this was no big deal since our pipeline is just code. But since it is code, we could go one step further. Our pipeline could read the
.tool-versionsfile and use that information to build the container image that gets deployed to production. That's exactly what this change does.The only runtime dependency version that does not exist in
.tool-versionsis the OS - Ubuntu 22.04 in production. This is a reasonable limitation that we could improve as a follow-up. What I am thinking right now is that we should NOT depend on an OS for the production container image, and instead finish the migration to Elixir (Erlang) releases + one of those sweethttps://github.com/chainguard-images/images#chainguard-images, maybe https://github.com/chainguard-images/images/tree/main/images/glibc-dynamic . What we are really missing is an Elixir Chainguard image. One day...
Boy scout fixes:
go mod tidyflyctlversion to latestyarn,flyctl&mageviaasdfmagecommands instead ofgo run main.go -w ..asdfon a fresh macOS 16.3 (arm64)asdfon Debian 11TODO
CONTRIBUTING.mdby running on a fresh macOS.devcontainer/docker-compose.yml