Bump docker dependency to v20.10.0-beta

[nkubala]

Summary

Updates the version of the docker/docker dependency to v20.10.0-beta, specifically to match moby/buildkit.

Selfishly, this is done so that we can resolve a dependency issue in https://github.com/GoogleContainerTools/skaffold, where we vendor both buildkit and pack.

This change is non-functional.

Output

N/A

Documentation

• Should this change be documented?
  • Yes, see #___
  • No

Related

Resolves #___

[nkubala]

looks like make verify-format is failing because the imports in the generated files got moved around. I generated this code with make generate so I'm not sure why this is happening...should I fix manually?

[dfreilich]

Hey @nkubala , thanks for the PR! Yes, if you could fix the imports (either by hand or by make tidy) to get these checks passing, that would be great.

[codecov]

Codecov Report

Merging #960 (4c5b36a) into main (9304f5a) will not change coverage.
The diff coverage is 33.34%.

@@           Coverage Diff           @@
##             main     #960   +/-   ##
=======================================
  Coverage   77.63%   77.63%           
=======================================
  Files         103      103           
  Lines        5005     5005           
=======================================
  Hits         3885     3885           
  Misses        725      725           
  Partials      395      395           

Flag	Coverage Δ
os_linux	77.63% <33.34%> (+0.06%)	⬆️
os_macos	74.61% <0.00%> (+0.04%)	⬆️
os_windows	100.00% <ø> (ø)
unit	77.63% <33.34%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[nkubala]

@dfreilich fixed everything up. codecov is failing, but since this doesn't really introduce any new code i'm not sure how to fix it apart from writing you guys some new tests :) let me know what i should do.

[jromero]

@nkubala I'm sure we can overlook codecov :D

We recently ran into dependency issue in relation to docker (aka moby/moby). You can see the details here. I realize that this is a newer version and that given the fact that it compiles and none of the tests fail, it should provide a higher level of compatibility.

Out of curiosity, have you requested that this newer version also be update in go-containerregistry. I see that skaffold also uses go-containerregistry.

[nkubala]

@jromero haven't we all run into dependency issues with moby/moby 😆 hopefully this change will only alleviate some pain in the future though.

i haven't bumped go-containerregistry yet, but it was a source of several transitive dependencies that cause pain in skaffold so it'll likely be next up :)

is this PR ok to merge?

[jromero]

Let's give it a shot. 🤞

If we find some issues we will have to revert.

[nkubala]

sounds good, if it ends up getting reverted tag me and i can try and look again.