D4no0
Avoiding debian version for hexpm elixir images
I am currently trying to setup a CI that will build the docker image of the project. The caveat is that I am trying to use .tool-versions as the source of truth both for dev/CI and docker image.
So far I managed to pass correctly the necessary build arguments to docker build, however having the OS in format buster-20240612-slim makes it really hard to change elixir/erlang versions without eventually hitting into the situation where for a specific OS the versions are missing.
I am currently using base images from hexpm/elixir.
Maybe I missed something, but is it possible to somehow skip setting OS version? as I don’t care that much what version of the distribution is running.
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 5 of 5 Posts
joelpaulkoch
You are trying to use
.tool-versionsas the source of truth for everything, right?So, is your plan to get any debian image and install erlang/elixir using
asdfinside the docker image, then proceed and build the project?Why could the elixir/erlang versions be missing for a specific OS when you install them using asdf?
D4no0
Exactly.
No, I want a pre-built base image with elixir/erlang, I am not planning on building erlang from source inside of docker. I am currently using the images from hexpm/elixir forgot to mention that. Think of
.tool-versionsas just a txt document with the right versions, asasdfis used only on dev environment.The main problem I am encountering is that pre-built images by hex have also their OS versioned, so this makes it hard as some elixir/erlang versions are using older OS versions, for example: 1.10.4-erlang-21.0.9-debian-bullseye-20241111-slim
LostKobrakai
I don’t think there are tags for that repo, which do not include OS level details.
joelpaulkoch
Oh, I see. I guess you could make a call to the docker hub api to get the latest tags, then filter based on your versions..
LostKobrakai
That’s also well cacheable given tags never change.