Enable ssh forwarding when building a remote target#3050
Enable ssh forwarding when building a remote target#3050thaJeztah merged 1 commit intodocker:masterfrom
Conversation
|
@tonistiigi @crazy-max ptal |
Codecov Report
@@ Coverage Diff @@
## master #3050 +/- ##
==========================================
- Coverage 57.99% 57.98% -0.02%
==========================================
Files 302 302
Lines 21748 21754 +6
==========================================
Hits 12613 12613
- Misses 8212 8218 +6
Partials 923 923 |
|
@alexcb Validation + DCO broken |
|
It looks like the buildkit dependency version change that @thaJeztah and I made yesterday broke it #3050 (comment) I suspect we'll need to update the 0.8 branch in the end (to include my PRs up until d3e0a6f2d8c36dcd2d785ab436ead8bd2dc50f28) to make this PR work. Should I open another PR against https://github.com/moby/buildkit/tree/v0.8 with the required cherry-picks to make this work? |
|
If you need something from master branch that isn't in |
Does this mean I can re-enable my change to |
|
Yes, @thaJeztah said that the commits you needed should have already been in the release tag. If this is not true then vendor the commit you need. |
c551a1e to
f4e935f
Compare
|
thanks for the help @tonistiigi , I rebased this PR off master and the tests are once again passing. |
|
Would love to get this merged @alexcb! |
|
I'm looking forward for this fix to be merged, would solve a problem with one of my builds. |
- this fixes moby/buildkit#2040 by enabling ssh forwarding when a remote address is given on the command line, this is a similar fix to docker/buildx#581 Signed-off-by: Alex Couture-Beil <alex@earthly.dev>
f4e935f to
af1bb80
Compare
this fixes moby/buildkit#2040 by enabling ssh forwarding when a remote address is given on the command line, this is a similar fix to docker/buildx#581
previously when I ran:
I could replicate the issue and would get this error:
However now with this fix, I get a much more appropriate error showing that my git clone failed:
and when I point it at an actual private repo, it can authenticate and builds as expected.