We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I installed colima, docker and docker-compose from homebrew. (brew install colima && brew install docker && brew install docker-compose).
brew install colima && brew install docker && brew install docker-compose
So I ran composer start, and I saw the following issue when trying to run the docker-compose up in my project.
composer start
docker-compose up
no matching manifest for Linux/arm64/v8 in the manifest list entries
I'm using an M1 chip.
I found this post https://onexlab-io.medium.com/apple-m1-chip-no-matching-manifest-for-linux-arm64-v8-docker-mysql-5142060a9309, and I was able to fix that by adding the plataform in my docker-compose.yml.
plataform
docker-compose.yml
My question is if it's really expected or if it shouldn't happen with colima?
colima
Thank you!
The text was updated successfully, but these errors were encountered:
I think that would be the expected behaviour i.e. you get an error when the requested image is not available for your machine type/platform.
Sorry, something went wrong.
No branches or pull requests
I installed colima, docker and docker-compose from homebrew. (
brew install colima && brew install docker && brew install docker-compose
).So I ran
composer start
, and I saw the following issue when trying to run thedocker-compose up
in my project.I'm using an M1 chip.
I found this post https://onexlab-io.medium.com/apple-m1-chip-no-matching-manifest-for-linux-arm64-v8-docker-mysql-5142060a9309, and I was able to fix that by adding the
plataform
in mydocker-compose.yml
.My question is if it's really expected or if it shouldn't happen with
colima
?Thank you!
The text was updated successfully, but these errors were encountered: