-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
Publish Docker images to GitHub Container Registry #5032
Conversation
In addition to publishing Docker images to Docker Hub, also publish to GitHub Container Registry. Signed-off-by: Mark S. Lewis <[email protected]>
Note that when running this on my own fork, I observed the following failures on the Docker build and publish steps. I don't believe these failures are related to this change; just indicate a possible existing problem in the codebase. Peer
Orderer
|
Thanks @bestbeforetoday
I'll go ahead and merge this PR (and backport to release-2.5) since this is not related to the above problem. |
how much time do I have to figure it out before rolling back the change to github.com/prometheus/client_golang? |
@pfi79 Not urgent since we are not planning a release in the short term... maybe a week? |
I'm afraid I won't make it. So now I will send a pr that will roll back the prometheus/client_golang changes. The working branch is more important in my opinion. I will continue the research. So far I found that docker builds if you delete the vendor folder. But it doesn't build with the vendor folder. I also asked the developers of the library. I had a very interesting conversation with the bot. But the conversation went in circles. |
In addition to publishing Docker images to Docker Hub, also publish to GitHub Container Registry.
Contributes to #4998