MariaDB image for apple M1

zestagio commented 1 year ago

Hello, I saw this issue and comment https://github.com/wodby/docker4drupal/issues/465#issuecomment-785844022. According to this comment the mariaDB supports arm64, but for me it does not look like true:

Output of docker inspect $(docker images | grep "wodby/mariadb" | awk '{ print $3 }') -f '{{.Architecture}}'

amd64

So, is it expected behavior and everything is fine or I have to configure something?

Output of docker info

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.8.2)
  compose: Docker Compose (Docker Inc., v2.6.1)
  extension: Manages Docker extensions (Docker Inc., v0.2.7)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
  scan: Docker Scan (Docker Inc., v0.17.0)

Server:
 Containers: 3
  Running: 3
  Paused: 0
  Stopped: 0
 Images: 3
 Server Version: 20.10.17
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
 runc version: v1.1.2-0-ga916309
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.10.104-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 1
 Total Memory: 1.928GiB
 Name: docker-desktop
 ID: FKWQ:LLHO:Q72C:MXUA:EONZ:T6US:HZ5N:X2CU:JTZR:RIPH:QD7L:74ZT
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5000
  127.0.0.0/8
 Live Restore Enabled: false

Contents of your docker-compose.yml

version: "3"

services:
  mariadb:
    image: wodby/mariadb:$MARIADB_TAG
    container_name: "${PROJECT_NAME}_mariadb"
    stop_grace_period: 30s
    environment:
      MYSQL_ROOT_PASSWORD: $DB_ROOT_PASSWORD
      MYSQL_DATABASE: $DB_NAME
      MYSQL_USER: $DB_USER
      MYSQL_PASSWORD: $DB_PASSWORD
    ports:
      - "3306:3306"

Contents of your .env

DB_ROOT_PASSWORD=password
DB_NAME=drupal
DB_USER=drupal
DB_PASSWORD=drupal

MARIADB_TAG=10.8-3.21.2

csandanov commented 1 year ago

we've removed the builds for arm64 for now because the cross-compilation doesn't fit in gh actions 6 hours limit and gh actions has no arm64 machines support https://github.com/wodby/mariadb/issues/36

zestagio commented 1 year ago

Clear, do you have any plans to solve it somehow in the future?

kvantstudio commented 1 year ago

Clear, do you have any plans to solve it somehow in the future?

I am using image: arm64v8/mariadb:10.3. Work fast and fine

elaman commented 1 year ago

I know it would be better to have ARM images for MariaDB, but for those who just wants to get their project started, the latest wodby/mariadb image that supports M1 is 10.4-3.13.21, so you can use it in your .env file like so:

MARIADB_TAG=10.4-3.13.21

sandykadam commented 7 months ago

Can we please have a fix for this asap?

wodby / docker4drupal

MariaDB image for apple M1 #526