Open marcelorodrigo opened 4 weeks ago
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.
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.
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.
@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?
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:
If I read the comments about it right, it was fixed and we were planning on removing that part.
let me first solve the issues there before you merge to dev.
Okay, please let me know when it can be merged.
Description:
When attempting to pull the MySQL image on an ARM64 architecture (such as Apple Silicon Mac), Docker Compose fails with the error:
Steps to Reproduce:
docker compose up
.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:
Request:
Please add an ARM64-compatible manifest for the MySQL Docker image, or recommend an ARM-native image for MySQL.