You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got some docker-compose configuration for legacy project in which I need to run percona which doesn't support my M1 mac - so I used linux/amd64 version of that image. Before updating docker-compose (via brew) to version 2.11.x, everything seems to work fine. After updates, it totally skips information on which platform build needs to be created.
Can you post the output of docker-compose version with a dash please?
Something is strange in you logs output, the docker info mentioned a version v2.10.2 of Compose and the docker compose version a v2.11.0 🤔
Description
Can be reelated somehow to:
I got some docker-compose configuration for legacy project in which I need to run
percona
which doesn't support my M1 mac - so I usedlinux/amd64
version of that image. Before updatingdocker-compose
(viabrew
) to version 2.11.x, everything seems to work fine. After updates, it totally skips information on which platform build needs to be created.sample
docker-compose.yml
:docker/percona/Dockerfile
It also doesn't works with that kind of config:
Using
docker build
withoutdocker-compose
builds that image correctly:docker build ./docker/percona/ -t percona-test --platform=linux/amd64
Using platform without a custom build also works fine:
Also percona image from which I'm building has a correct manifest for amd64:
Steps to reproduce the issue:
docker-compose.yml
andDockerfile
as in the upper samplesdocker-compose up
Describe the results you received:
Describe the results you expected:
Container was up, as linux/amd64
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker compose version
:Output of
docker-compose version
: (which I'm using)Output of
docker info
:Additional environment details:
MacBook Pro 2021
Apple M1 Pro
macOS 12.5.1
brew version:
The text was updated successfully, but these errors were encountered: