[MDEV-11847] aarch64/mariadb for hub.docker.com Created: 2017-01-19 Updated: 2021-02-01 Resolved: 2021-02-01 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Compiling |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Minor |
| Reporter: | Tobias | Assignee: | Alexey Bychko (Inactive) |
| Resolution: | Won't Fix | Votes: | 2 |
| Labels: | ARM, ARMv8, CI, Docker, aarch64 | ||
| Description |
|
Hey, is it possible that you update your build system to support the aarch64 ARMv8 architecture? Or what do you need to do that? https://hub.docker.com/u/aarch64/ / https://github.com/docker-library/official-images The Docker Hub is depending on the files from the upstream build system. So it would be very nice if you add that in the future. Best Regards, |
| Comments |
| Comment by Sergei Golubchik [ 2017-05-26 ] |
|
Yes. We don't have a aarch64 builder at the moment, but we'd like to have one later on. There's a work underway to make MariaDB/MySQL work better on this architecture. |
| Comment by Edward Vielmetti [ 2017-07-11 ] |
|
In the meantime I am using https://hub.docker.com/r/lsioarmhf/mariadb-aarch64/ as a community supported arm64 version. |
| Comment by Daniel Black [ 2018-05-01 ] |
|
docker-library folks are working on it: https://github.com/docker-library/mariadb/issues/125 |
| Comment by Daniel Black [ 2021-02-01 ] |
|
Seems https://hub.docker.com/u/aarch64/ has moved to https://hub.docker.com/u/arm64v8/ and is actively getting updates from other projects. MariaDB gained arm64v8 support on 3 August 2018 (https://github.com/docker-library/official-images/pull/4674). Since then every 10.1+ release has included amd64 support (http://soaphub.org/imagehub/?q=mariadb&n=library&p=1). Since architecture specific domains for containers where an artifact of lack of poor multiarch support I don't think this is still the case. I haven't seen a user having trouble accessing the mariadb container images for arm64. With the current high level of multiarch tools in the consumption of images adding a separate release location after 2 years doesn't seem to be worth it. Contrary evidence as to why a separate domain is still useful is welcome. |