# 1.10.7-alpine docker tag missing

**URL:** <https://discourse.julialang.org/t/1-10-7-alpine-docker-tag-missing/124817>\
**Category:** New to Julia\
**Created:** [January 16, 2025, 6:26am UTC](https://discourse.julialang.org/t/1-10-7-alpine-docker-tag-missing/124817 "2025-01-16T06:26:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nsslh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nsslh/32/27447_2.png) [@nsslh](https://discourse.julialang.org/u/nsslh)\
**Post date:** [January 16, 2025, 6:26am UTC](https://discourse.julialang.org/t/1-10-7-alpine-docker-tag-missing/124817/1 "2025-01-16T06:26:55Z")

</div>

I need to update a few of my docker container services to Julia 1.10.7. They are `FROM julia:1.10.2-alpine3.19`. I expected to be able to affect the upgrade with `FROM julia:1.10.7-alpine3.20` or `FROM julia:1.10.7-alpine3.21`.

However, I can find no tags for `1.10.7-alpine` at all. Is this an accidental gap or a change of release strategy for LTS?

I have to go through a security review if I switch my base images away from Alpine. So I have a strong preference to stick with Alpine, and a moderate preference to not build base images myself.

What should I do?

---

<div class="post-metadata">

**Author:** ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)\
**Post date:** [January 16, 2025, 8:48am UTC](https://discourse.julialang.org/t/1-10-7-alpine-docker-tag-missing/124817/2 "2025-01-16T08:48:31Z")

</div>

Alpine for 1.10 was removed in [Update 1.10 to 1.10.7 · docker-library/julia@20763c0 · GitHub](https://github.com/docker-library/julia/commit/20763c0a7c195e9a57eb7903ff60e8b6a811e4fe) and [Update julia by tianon · Pull Request #17981 · docker-library/official-images · GitHub](https://github.com/docker-library/official-images/pull/17981) probably because there is no official build for it.

---

<div class="post-metadata">

**Author:** ![nsslh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nsslh/32/27447_2.png) [@nsslh](https://discourse.julialang.org/u/nsslh)\
**Post date:** [January 16, 2025, 3:15pm UTC](https://discourse.julialang.org/t/1-10-7-alpine-docker-tag-missing/124817/3 "2025-01-16T15:15:20Z")

</div>

It surprises me that LTS has dropped support for Alpine, while STABLE retains it.

---

<div class="post-metadata">

**Author:** ![denial768](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@denial768](https://discourse.julialang.org/u/denial768)\
**Post date:** [January 20, 2025, 5:29am UTC](https://discourse.julialang.org/t/1-10-7-alpine-docker-tag-missing/124817/4 "2025-01-20T05:29:35Z")

</div>

This post was temporarily hidden by the community for possibly being off-topic, unfocused, inappropriate, or spammy.

---

<div class="post-metadata">

**Author:** ![nsslh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nsslh/32/27447_2.png) [@nsslh](https://discourse.julialang.org/u/nsslh)\
**Post date:** [January 24, 2025, 6:57am UTC](https://discourse.julialang.org/t/1-10-7-alpine-docker-tag-missing/124817/5 "2025-01-24T06:57:01Z")

</div>

Having had time to think, I don’t really understand this explanation. Here is the Dockerfile for an Alpine-based 1.10.8: [julia/1.10/alpine3.21/Dockerfile at master · docker-library/julia · GitHub](https://github.com/docker-library/julia/blob/master/1.10/alpine3.21/Dockerfile)

Why isn’t it being built, tagged and pushed to Docker Hub?

---

<div class="post-metadata">

**Author:** ![nsslh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nsslh/32/27447_2.png) [@nsslh](https://discourse.julialang.org/u/nsslh)\
**Post date:** [January 24, 2025, 7:06am UTC](https://discourse.julialang.org/t/1-10-7-alpine-docker-tag-missing/124817/6 "2025-01-24T07:06:58Z")

</div>

Ha, I was wrong. The 1.10.8-alpine3.20 and 1.10.8-alpine3.21 tags are now available on Docker Hub. I think there was a release engineering mistake with 1.10.7, is all.