/cc @SamWhited

There was some concern related to using the replace directive in c6641fb; not sure I follow it completely.

The issue with replace is that it's not transitive. Anything importing a package in the buildkit module would not see the replace directive, and would select a different version of containerd than the one required. Put another way: replace is for main packages, not for libraries.

@SamWhited Thanks! That makes sense.

@AkihiroSuda I've made the same changes you made in yours, still works with go1.13 (tested with version 1.13.4). Travis failed at the "Cross" step, but I haven't been able to replicate any failures locally.

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:

$ git clone -b "fix-go-mod" git@github.com:zachbadgett/buildkit.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842354378440
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

@AkihiroSuda Tracked down the issue, it was coming from the docker version you wanted to use. There were a couple dependency issues.

Issue 1:
From this commit: moby/moby@6b91cef docker moved to using osversion from github.com/Microsoft/hcsshim to get the windows OS version, however, osversion.Build() was not added until v0.8.7 in this commit: microsoft/hcsshim@92cb5b6 and buildkit was on v0.8.5.

Issue 2:
From this commit:
moby/moby@c3a0a37#diff-d56bbc14384133b2bc2cf0677bb3561bR105
Using windows.SecurityDescriptorFromString which was not added to sys until golang/sys@14da1ac#diff-c4ffa695b270239c949ef5b31be6c4f5R1317 and buildkit was on v0.0.0-20190812073006-9eafafc0a87e which did not include that change.

however, osversion.Build() was not added until v0.8.7 in this commit: microsoft/hcsshim@92cb5b6 and buildkit was on v0.8.5.

Be aware that tags should no longer be used from that repository. See microsoft/hcsshim#700

This is a code-only repository and does not have a stable release. 0.8.6 is the last tagged release, and it is out of date for ContainerD and Kubernetes. Downstream projects should vendor in this codebase using commit ids instead of tags, then validate fixes and do a full test pass of the whole project.

Unfortunately, go mod has no option for a repository to indicate "don't use tags" 😞

@thaJeztah buildkit does not have a direct dependency on microsoft/hcsshi. Only indirectly through docker and another library called fsutil (which uses v0.8.5); so using the tag that satisfies docker as well seems appropriate. Let me know if anyone disagrees or if anyone has a commit they would like me to switch to and I'll be happy to update it :)

I have the same error when I want to import buildkit via go.mod

go: github.com/moby/buildkit@v0.6.3 requires
	github.com/containerd/containerd@v1.3.0-0.20190507210959-7c1e88399ec0: invalid pseudo-version: version before v1.3.0 would have negative patch number

Any plan to merge the fix ?

@tonistiigi @tiborvass @thaJeztah PTAL?

@zachbadgett could you rebase and update the PR with replace directives?

sorry needs rebase again

@tonistiigi PTAL at replace directives?

On the pseudo-version issues, is there any chance of the relevant upstream projects (containerd and docker, in this case) putting tags like v1.4.0-alpha.0 (in the case of containerd) on their master branch, on the commit after the previous release branched off?

(Without testing...) then go would pick those up, generate useful pseudo-versions, and we could avoid all the issues around replace in go.mod and having a higher-tagged-but-older version be selected for module resolution.

For containerd there's containerd/containerd#3031 and containerd/containerd#3554 tracking go mod compatibility.

needs rebase again

My mistake, I thought I ran make test before committing.

@tonistiigi : Can we merge this as-is and address other issues in follow-up PRs?

@AkihiroSuda I'm fine with the replace rules but rolling back deps if they are already too new is going to be a pain. Feel free to carry this with extra commits to adjust containerd dependencies to the correct version to get this merged. And while you are at it, update to Dockerfile as well so we see this(and go.mod validation) in action.

carried in #1376