Details

    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,
      Tobias

      Attachments

        Activity

          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.

          serg Sergei Golubchik added a comment - 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.

          In the meantime I am using

          https://hub.docker.com/r/lsioarmhf/mariadb-aarch64/

          as a community supported arm64 version.

          vielmetti Edward Vielmetti added a comment - In the meantime I am using https://hub.docker.com/r/lsioarmhf/mariadb-aarch64/ as a community supported arm64 version.
          danblack Daniel Black added a comment -

          docker-library folks are working on it: https://github.com/docker-library/mariadb/issues/125

          danblack Daniel Black added a comment - docker-library folks are working on it: https://github.com/docker-library/mariadb/issues/125
          danblack Daniel Black added a comment -

          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.

          danblack Daniel Black added a comment - 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.

          People

            abychko Alexey Bychko (Inactive)
            Sachs Tobias
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.