-
-
Notifications
You must be signed in to change notification settings - Fork 931
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: docker buildx context error #4401
Conversation
It's a little weird. The message isn't quite what it should be though:
while the error is
Any idea why it's such a mixture? |
probably some other function is wrapping it, lemme clone your branch and take a look |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the proposed changes fixed it to me:
• docker images
• building docker image image=goreleaser/goreleaser:v1.21.3-next-arm64
• building docker image image=goreleaser/goreleaser:v1.21.3-next-amd64
• took: 2s
⨯ release failed after 12s error=docker build failed: docker buildx not set to default context, please switch using 'docker context use default'
Learn more at https://goreleaser.com/errors/docker-build
no problem! I usually squash merge PRs, so its all good :) |
also sorry for the delay, dunno what happened, I was debugging this, something happened, and I forgot it for 24hrs for some reason |
Co-authored-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>
Co-authored-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>
No worries. Still much quicker than expected :) The changes made sense. |
Codecov Report
@@ Coverage Diff @@
## main #4401 +/- ##
==========================================
- Coverage 83.87% 83.85% -0.02%
==========================================
Files 133 133
Lines 12727 12732 +5
==========================================
+ Hits 10675 10677 +2
- Misses 1635 1637 +2
- Partials 417 418 +1
|
Provide more context for the error message and point to the documentation.
It gives the users more context on the error and instructions to fix the problem.
Fixes the issue discussed in #4392
Sorry for the commit message formats. Read that too late.
I hope you can fix that using a "squash and merge"?