-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Image no longer works in GitHub Actions #29
Comments
interesting, so this does not work? needs to be a wildcard |
Oh, I didn't know that was even in there! No, the It might still be broken in actions because the global config doesn't seem to exist properly. Let me test with the latest |
try image from |
Appears to be unresolved:
The error "not a git repository" is due to the I will build and try |
i think the best option would be to keep an extra run step instead of adding it goreleaser-cross and wait till |
For those who are facing the same issue, here is a fix: jobs:
goreleaser:
runs-on: ubuntu-latest
container:
image: goreleaser/goreleaser-cross
environment: build
steps:
- name: Checkout
uses: actions/checkout@v3
with:
fetch-depth: 0
- name: Workaround Git Security Warning
run: |
# Workaround a bug in github actions:
git config --global --add safe.directory "$GITHUB_WORKSPACE"
- name: Set up Go
uses: actions/setup-go@v2
with:
go-version: 1.19 |
Hey guys!
The error is: Any suggestions? Thank you |
how do you mount workdir to docker? |
Hi troian, this is the full command:
|
do you use custom entry point |
Due to a bug in actions/checkout, this action cannot be used as a container without an additional step:
This is not unique to
goreleaser-cross
and will affect all versions until actions/checkout is fixed.But, in the meantime, there is a method we can apply to the image that will allow it work without that extra step in the workflows. We could bake the command into the image itself with something like:
This would effectively disable the safe directory functionality within the goreleaser-cross container.
The text was updated successfully, but these errors were encountered: