new glibc + old docker impacting DockerHub #1

Open
opened 8 months ago by wanderer Β· 0 comments
Owner

Alright, let me tell you what this is all about. πŸ‹

Docker builds (locally and also in DockerHub) started failing after glibc 3.34 has been updated during jan-feb 2021 and thas caught me on both fedora 33 and archlinux workstation/server boxes (talking OS, not containers now).

A hotfix patch has been issued as a workaround to remedy failing builds - bd4c5abe4d.

Recently, I have started building moby from sources myself (moby is docker-{c,e}e's upstream that's directly being shipped on fedora instad of the "docker-*" product) and installed it on my fedora 33 box, while archlinux gradually updated to a fairly recent docker (Docker version 20.10.5, build 363e9a88a1 as of writing).

Latest moby commit on which I was able to run docker build for this image on fedora 33 was dbc3365da2.

For these reasons I decided to revert the hotfix just today in dbeddd89be, after which DockerHub builds started to fail again.

That is because Dockerhub build servers are probably not running a latest master moby/docker and as such don't have the necessary fixes required to build images that run glibc >=3.34 (see the original hotfix commit message for more reasoning and references).

That basically means that until they (the DockerHub) run a reasonably recent docker/moby, we're going to see just more of dockerhub build: failing and anyone expecting these images to work will either have to update in a similar fashion to what I've done or wait until the patched versions reach whatever distro you're using.

Unless that distro happens to be Arch, cause then you're ok anyway :D 🐳

Alright, let me tell you what this is all about. πŸ‹ Docker builds (locally and also in DockerHub) started failing after glibc 3.34 has been updated during jan-feb 2021 and thas caught me on both fedora 33 and archlinux workstation/server boxes (talking OS, not containers now). A hotfix patch has been issued as a workaround to remedy failing builds - https://git.dotya.ml/wanderer/docker-archlinux/commit/bd4c5abe4dca475965548cb8332ef9b9d2a4953c. Recently, I have started building [`moby`](https://github.com/moby/moby) from sources myself (moby is `docker-{c,e}e`'s upstream that's directly being shipped on fedora instad of the "docker-\*" product) and installed it on my fedora 33 box, while archlinux gradually updated to a fairly recent docker (`Docker version 20.10.5, build 363e9a88a1` as of writing). Latest `moby` commit on which I was able to run `docker build` for this image on fedora 33 was [`dbc3365da2`](https://github.com/moby/moby/commit/dbc3365da22ce76367ccaad79248c9a98332d80d). For these reasons I decided to revert the hotfix just today in [`dbeddd89be`](https://git.dotya.ml/wanderer/docker-archlinux/commit/dbeddd89be6bdb04c7e859a30e9e80d7e7175cba), after which DockerHub builds started to fail again. That is because Dockerhub build servers are probably not running a latest master `moby`/`docker` and as such don't have the necessary fixes required to build images that run glibc >=3.34 (see the original hotfix commit message for more reasoning and references). That basically means that until they (the DockerHub) run a reasonably recent docker/moby, we're going to see just more of `dockerhub build: failing` and anyone expecting these images to work will either have to update in a similar fashion to what I've done or wait until the patched versions reach whatever distro you're using. Unless that distro happens to be Arch, cause then you're ok anyway :D 🐳
wanderer added the
bug
label 8 months ago
wanderer added the
upstream-related
label 8 months ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.