Skip to content

Conversation

@thaJeztah
Copy link
Member

relates to:

commit 043dbc0 (#44686) temporarily switched to a fork of BuildKit to workaround a failure in CI. These fixes have been backported to the v0.11 branch in BuildKit, so we can switch back to upstream.

We can remove this override once we update vendor.mod to BuildKit v0.11.3.

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

@crazy-max
Copy link
Member

https://github.com/moby/moby/actions/runs/4102538542/jobs/7075796769#step:6:13

fatal: detected dubious ownership in repository at '/go/src/github.com/docker/docker'
To add an exception for this directory, call:

	git config --global --add safe.directory /go/src/github.com/docker/docker

Might need https://github.com/moby/moby/pull/43529/files#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557R637-R638

# set dev environment as safe git directory
RUN git config --global --add safe.directory $GOPATH/src/github.com/docker/docker

@thaJeztah
Copy link
Member Author

Interesting; wondering where the "dubious ownership" would come from, as all steps would run with the same user?

commit 043dbc0 temporarily switched to a
fork of BuildKit to workaround a failure in CI. These fixes have been
backported to the v0.11 branch in BuildKit, so we can switch back to upstream.

We can remove this override once we update vendor.mod to BuildKit v0.11.3.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
@thaJeztah thaJeztah force-pushed the gha_remove_buildkit_override branch from a24e078 to e564932 Compare February 6, 2023 17:09
@thaJeztah thaJeztah changed the title gha: switch back to upstream for testing gha: switch buildkit back to upstream for testing Feb 6, 2023
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.

3 participants