Error response from daemon: experimental session with v1 builder is no longer supported, use builder version v2 (BuildKit) instead

[jscontreras]

Bug

Current Behavior

Following the demo instructions using the latest Docker Desktop 2.4..0.0

# when I run
garden deploy

the error

Error response from daemon: experimental session with v1 builder is no longer supported, use builder version v2 (BuildKit) instead

Here's the full output:

Sending build context to Docker daemon  13.82kB
Error response from daemon: experimental session with v1 builder is no longer supported, use builder version v2 (BuildKit) instead

Expected behavior

It should build and deploy to kubernetes correctly

Reproducible example

Workaround

Suggested solution(s)

Additional context

Your environment

• OS: macOS Catalina 10.15.7
• How I'm running Kubernetes: Docker Desktop 2.4.0.0

garden version
0.12.9

[edvald]

I suspect this is a similar problem as this issue: k3s-io/k3s#1708

Basically it appears they've changed their API somewhat in the latest version, so we need to look into how we can address that in a way that works across the new version and older versions as well.

[eysi09]

Hi @jscontreras

I've been unable to reproduce this on my end. Would you mind sharing your provider configuration?

[eysi09]

Scratch that, I'm seeing this issue on my end as well now.

[jscontreras]

Oh I'm glad you are seeing it too! Thanks for looking into this. Is kind of an issue that this is happening with the official getting started documentation (maybe add a note while you guys fix it?) I lost a ton of time thinking I was doing something wrong
Thanks

[eysi09]

Yeah good point. I'm hope to be able to roll out a fix later today. But in the meantime, the following should do the trick:

1. Open Docker for Desktop preferences.
2. Click Docker Engine tab.
3. Add "features": { "buildkit": true } in the input field.

See also:

[eysi09]

Looks like this was an issue with Docker all along. The offending code was removed in this commit: docker/docker-ce@95971a4, but it hasn't been released yet.

I'm not sure there's much we can do about this on our end except ask users to do one of the following:

• Downgrade the Docker CE (i.e Docker for Desktop) server version (to 19.x.y, I believe), or
• upgrade the Docker CLI version (to 20.x.y, I believe), or
• apply the fix in my previous comment.

There was also a question about this on StackOverflow, here's my answer, in case the conversation turns up more useful information.

I'll also make sure to add an entry on this in the Troubleshooting section of our docs.