# Automatically building and releasing Erlang docker images

**URL:** <https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889>\
**Category:** Chat / Discussions\
**Tags:** docker, packages\
**Created:** [September 21, 2023, 1:16pm UTC](https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889 "2023-09-21T13:16:38Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![asabil](https://erlangforums.com/user_avatar/erlangforums.com/asabil/32/381_2.png) [@asabil](https://erlangforums.com/u/asabil)\
**Post date:** [September 21, 2023, 1:16pm UTC](https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889/1 "2023-09-21T13:16:38Z")

</div>

Hi,

I was wondering if it could make sense to automatically start building and releasing the Erlang docker images upon each release by making use of Github Actions? Is this something that the OTP team would be interested in?

This also could be an opportunity to improve the Erlang docker image tagging scheme to include the base distro (bookworm vs bullseye) as discussed here: [update 26 branch debian base image by pilou- · Pull Request #447 · erlang/docker-erlang-otp · GitHub](https://github.com/erlang/docker-erlang-otp/pull/447)

---

<div class="post-metadata">

**Author:** ![LostKobrakai](https://erlangforums.com/user_avatar/erlangforums.com/lostkobrakai/32/453_2.png) [@LostKobrakai](https://erlangforums.com/u/LostKobrakai)\
**Post date:** [September 21, 2023, 1:42pm UTC](https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889/2 "2023-09-21T13:42:43Z")

</div>

> [@asabil](#):
>
> I was wondering if it could make sense to automatically start building and releasing the Erlang docker images upon each release by making use of Github Actions? Is this something that the OTP team would be interested in?

The hex team already has automations to do that: [Docker](https://hub.docker.com/r/hexpm/erlang)

---

<div class="post-metadata">

**Author:** ![asabil](https://erlangforums.com/user_avatar/erlangforums.com/asabil/32/381_2.png) [@asabil](https://erlangforums.com/u/asabil)\
**Post date:** [September 21, 2023, 8:28pm UTC](https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889/3 "2023-09-21T20:28:27Z")

</div>

Could we do the same for the official erlang docker images?

---

<div class="post-metadata">

**Author:** ![garazdawi](https://erlangforums.com/user_avatar/erlangforums.com/garazdawi/32/175_2.png) [@garazdawi](https://erlangforums.com/u/garazdawi)\
**Post date:** [September 22, 2023, 8:55am UTC](https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889/4 "2023-09-22T08:55:48Z")

</div>

> [@asabil](#):
>
> Is this something that the OTP team would be interested in?

While the repo for the Erlang images resides in our organization, we do not maintain them (just as we do not maintain [rebar3](https://github.com/erlang/rebar3)). So you will have to talk to the people maintaining those images.

---

<div class="post-metadata">

**Author:** ![tsloughter](https://erlangforums.com/user_avatar/erlangforums.com/tsloughter/32/418_2.png) [@tsloughter](https://erlangforums.com/u/tsloughter)\
**Post date:** [September 23, 2023, 6:55pm UTC](https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889/5 "2023-09-23T18:55:29Z")

</div>

But the otp repo is where release actions can be triggered. It wouldn’t need to actually build the docker image in the otp repo but it could send a webhook to the erlang/docker-erlang-otp github actions workflow could trigger and do the building.

Assuming maintainers of `erlang/docker-erlang-otp` are open to that do you think a PR to call the webhook may be accepted into `erlang/otp` repo?

---

<div class="post-metadata">

**Author:** ![garazdawi](https://erlangforums.com/user_avatar/erlangforums.com/garazdawi/32/175_2.png) [@garazdawi](https://erlangforums.com/u/garazdawi)\
**Post date:** [September 24, 2023, 9:20am UTC](https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889/6 "2023-09-24T09:20:52Z")

</div>

Yes, we have no problem with adding such a trigger.

---

<div class="post-metadata">

**Author:** ![starbelly](https://erlangforums.com/user_avatar/erlangforums.com/starbelly/32/209_2.png) [@starbelly](https://erlangforums.com/u/starbelly)\
**Post date:** [September 24, 2023, 7:10pm UTC](https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889/7 "2023-09-24T19:10:38Z")

</div>

This would be nice for the otp-macos repo that @paulo-f-oliveira and I are starting, though it doesn’t live under erlang org, so that might not be great security wise.

---

<div class="post-metadata">

**Author:** ![garazdawi](https://erlangforums.com/user_avatar/erlangforums.com/garazdawi/32/175_2.png) [@garazdawi](https://erlangforums.com/u/garazdawi)\
**Post date:** [September 25, 2023, 6:41am UTC](https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889/8 "2023-09-25T06:41:34Z")

</div>

I’m sure we can figure something out that would work and be secure for repos in other organizations as well.

---

<div class="post-metadata">

**Author:** ![adamu](https://erlangforums.com/user_avatar/erlangforums.com/adamu/32/2097_2.png) [@adamu](https://erlangforums.com/u/adamu)\
**Post date:** [September 26, 2023, 3:57pm UTC](https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889/9 "2023-09-26T15:57:34Z")

</div>

Considering that the “official” images are maintained by neither the erlang/elixir core teams, nor Docker, I think the name is quite a misnomer and a large source of confusion.

Over a year ago I attempted to add a note to the readme for the elixir image, highlighting some of the issues with these images and pointing people to the hexpm version, but it’s so far only helping the local dust population. [Update elixir to link to alternative and similarly official images by adamu · Pull Request #2206 · docker-library/docs · GitHub](https://github.com/docker-library/docs/pull/2206)

I wonder if it would be worth trying to consolidate the “official” and hexpm images?

They behave quite differently, with the “official” ones retroactively upgrading the same tag with newer underlying underlying OS (and in Elixir’s case, OTP) layers. This _can_ be useful because you don’t need to opt in to every minor update. However, I think that most people would actually prefer the default behaviour of the hexpm images - where a tag contains the relevant version numbers and is never updated - if you want a new version, you use a new tag.

---

<div class="post-metadata">

**Author:** ![tsloughter](https://erlangforums.com/user_avatar/erlangforums.com/tsloughter/32/418_2.png) [@tsloughter](https://erlangforums.com/u/tsloughter)\
**Post date:** [October 1, 2023, 10:24pm UTC](https://erlangforums.com/t/automatically-building-and-releasing-erlang-docker-images/2889/10 "2023-10-01T22:24:03Z")

</div>

They can’t be fully consolidated because Docker requires images to be tagged the way the official Erlang and Elixir images are if they are to be official.
