-
-
Notifications
You must be signed in to change notification settings - Fork 937
Add support for publishing to GitHub Container Registry #5983
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
base: main
Are you sure you want to change the base?
Conversation
|
Related to that error:
docker/setup-buildx-action#291 So I'm guessing ghcr doesn't like dots in tag names? |
|
I fixed that one already. Now theres another error: |
|
The only things I could find were posts related to github actions. Maybe there's just a network blip with github not reading the tags fast enough? |
|
I don't see anything else related to |
|
Same error after restart Edit: Here are the docs btw: https://codeberg.org/woodpecker-plugins/docker-buildx/src/branch/main/docs.md#multi-registry-push-example |
|
https://codeberg.org/woodpecker-plugins/docker-buildx/issues/156 mentions tagging issue might be related to newlines not generating properly? |
|
try using |
This is about tags_file which we dont use.
Tried it and same error. Edit: set |
|
Maybe setting Daemon.Debug will provide some insights? Edit: Found setting in the plugin here https://codeberg.org/woodpecker-plugins/docker-buildx/src/commit/b77706d30da9f5c88ce7e2f3a03e4ef819902d1f/plugin/plugin.go#L17 |
32cdc51 to
2fe2802
Compare
|
Added |
|
I been looking at this again today since dockers registry hates renovate. While tag is documented I don't see anywhere in the plugins code that would load it in unless if its from another library... I also didn't find many other git repos that used "tag" setting, especially with multi repo. Could you try something like And see how that'd go? |
|
The tag is already being set in line 244. It seems like this is a bug with the CI plugin, opened an issue there: https://codeberg.org/woodpecker-plugins/docker-buildx/issues/310 |
Continued from #5979 by @seang96