Fix ARM64 builds by replacing AMD64-only base image

[Copilot]

GitHub Actions ARM64 builds were failing because quay.io/sclorg/mariadb-1011-c9s only supports AMD64.

Changes

• Base image: Replace with registry.access.redhat.com/ubi9/ubi:latest (multi-arch)
• MariaDB installation: Explicitly install MariaDB 10.11 from UBI9 repos
• User setup: Create default user (UID 1001) that Redis setup renames to frappe
• Code quality: Define MYSQL_UID and FRAPPE_UID as env vars instead of hardcoded values

# Before
FROM quay.io/sclorg/mariadb-1011-c9s AS builder

# After  
FROM registry.access.redhat.com/ubi9/ubi:latest AS builder
ENV MYSQL_UID=27 FRAPPE_UID=1001
RUN dnf -y module enable mariadb:10.11 && \
    INSTALL_PKGS="mariadb mariadb-server mariadb-server-utils mariadb-devel" && \
    dnf install -y --setopt=tsflags=nodocs $INSTALL_PKGS

S2I script compatibility maintained. Both AMD64 and ARM64 builds should now succeed.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• cdn01.quay.io
  • Triggering command: /usr/bin/skopeo skopeo inspect docker://quay.io/sclorg/mariadb-1011-c9s (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

check why the github actions failed

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.