Skip to content
New issue

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

keep the platform defined, in priority, via DOCKER_DEFAULT_PLATFORM o… #9866

Merged
merged 1 commit into from
Sep 26, 2022

Conversation

glours
Copy link
Contributor

@glours glours commented Sep 22, 2022

…r the service.plaform one if no build platforms provided

What I did
During a compose up when the DOCKER_DEFAULT_PLATFORM isn't set, the platform list is reset and the service.platform defined in the compose file isn't applied during the build step.
Now the DOCKER_DEFAULT_PLATFORM is applied if defined otherwise the service.platform is used (if existing of course)

Be aware that both are defined and not targeting the same platform you will get the following message (current behaviour):

image with reference `image-name:tag` was found but does not match the specified platform: wanted `service.platform value`, actual: `DOCKER_DEFAULT_PLATFORM value`

Related issue
fixes #9864

(not mandatory) A picture of a cute animal, if possible in relation with what you did
image

…r the service.plaform one if no build platforms provided

Signed-off-by: Guillaume Lours <[email protected]>
Copy link
Member

@nicksieger nicksieger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

docker-compose cannot build image for different architecture
3 participants