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

Always use build kit on deploy #11

Merged
merged 1 commit into from
Dec 17, 2020
Merged

Always use build kit on deploy #11

merged 1 commit into from
Dec 17, 2020

Conversation

codefromthecrypt
Copy link
Member

Using Docker 20.10 commands we used before now break like this:

image with reference sha256:6deb7d92f59f205ddaf95230bec403fd117ab8f509074f09a3fc6b108276d744 was found but does not match the specified platform: wanted linux/arm64, actual: linux/amd64

This switches to always use BUILDKIT=1 when pushing images, as Docker
changed behavior in 20.10 and it is more complex to figure out if we are
20.10 or not, and would be annoying to figure out what later versions
would do.

See moby/moby#41552

Using Docker 20.10 commands we used before now break like this:

```
image with reference sha256:6deb7d92f59f205ddaf95230bec403fd117ab8f509074f09a3fc6b108276d744 was found but does not match the specified platform: wanted linux/arm64, actual: linux/amd64
```

This switches to always use BUILDKIT=1 when pushing images, as Docker
changed behavior in 20.10 and it is more complex to figure out if we are
20.10 or not, and would be annoying to figure out what later versions
would do.

See moby/moby#41552
@codefromthecrypt codefromthecrypt merged commit 26d28fb into master Dec 17, 2020
@codefromthecrypt codefromthecrypt deleted the buildkit1 branch December 17, 2020 04:15
codefromthecrypt pushed a commit that referenced this pull request Dec 17, 2020
In #11, I tried to find a configuration that works both in Docker 19
and 20. However, this breaks the build.

This reverts the change as there are bugs popping up related on Docker
20 anyway, such as docker/buildx#475

We use Docker from the OS distribution, so unlikely to accidentally
walk into a Docker 20. In other words, when it becomes stable, we can
try again.
@codefromthecrypt
Copy link
Member Author

This didn't work, so reverted it until things in Docker 20 stabalize, ideally to the point it is possible to use the same syntax for both 19 and 20 31b4d18

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

Successfully merging this pull request may close these issues.

2 participants