No matching manifest for linux/arm64/v8 in the MySQL image manifest list entries

[marcelorodrigo]

Description:

When attempting to pull the MySQL image on an ARM64 architecture (such as Apple Silicon Mac), Docker Compose fails with the error:

[+] Pulling 2/26
 ✘ mysql Error        no matching manifest for linux/arm64/v8 in the manifest list entries

Steps to Reproduce:

• On an ARM64 machine, create the docker-compose.yml as suggested in the manual.
• Run docker compose up.
• Observe that Docker Compose fails to pull the image, displaying the architecture compatibility error.

Expected Behavior:

The mysql image should have a manifest entry that supports ARM64 architecture, allowing it to run natively on ARM-based systems.

Actual Behavior:

Docker Compose fails with the error no matching manifest for linux/arm64/v8

Environment:

System: Apple Silicon (ARM64 architecture)

Request:

Please add an ARM64-compatible manifest for the MySQL Docker image, or recommend an ARM-native image for MySQL.

[simjanos-dev]

Hi!

I dont understand docker very well, but ill take a look. Ive just noticed theres a PR already.

There is a note in the main readme in the troubleshooting section about this and a fix for it.

@sergiolaverde0 is the person who made 99% of the current docker process.

[sergiolaverde0]

This is weird, the image we use does support arm64, but apparently it isn't being pulled correctly. I will take a look into this.

[simjanos-dev]

This is weird, the image we use does support arm64, but apparently it isn't being pulled correctly. I will take a look into this.

We already had this issue twice, I think it even had a github issue. We made a note in the readme file, i think because we could not figure out what the issue is.

I can merge #367, right? I can only test it on linux.

[marcelorodrigo]

@simjanos-dev let me first solve the issues there before you merge to dev.
I think the healthcheck section also can be sanitized.

Any reason you have a custom command for the database container that the default does not work as expected?

[simjanos-dev]

If you mean the custom code that waits for the database to be set up, there was a reason, but i don't remember what it was.

There was a PR about it:

#282

If I read the comments about it right, it was fixed and we were planning on removing that part.

[simjanos-dev]

let me first solve the issues there before you merge to dev.

Okay, please let me know when it can be merged.