-
Notifications
You must be signed in to change notification settings - Fork 21
Put Docker image for the GitHub triage action in the kubeflow docker hub registry #66
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
We have the kubeflow github organization We have the kubeflowrobot account for automating pushes to kubeflow I created a personal access token for this account. This is currently stored in google's internal secret management system; Google team can access it. I replaced the DOCKER_USERNAME and DOCKER_PASSWORD secrets on kubeflow/code-intelligence with kubeflowrobot and the associated access token. |
…ue_triage. * Instead of storing the image in a personal account we should use the kubeflow organization. * Related to kubeflow/code-intelligence#66
…ue_triage (#67) * Use the Kubeflow DockerHub organization for the GitHub action for issue_triage. * Instead of storing the image in a personal account we should use the kubeflow organization. * Related to #66 * Update the readme. * Update the issue_triage workflow to use the master version of the action. * Provide more explanation in the README including instructions for how to deploy.
When the action triggered we got a permission error trying to push to DockerHub |
I'm going to try reproducing it locally; by logging in as the kubeflow robot to docker and building the image. I got the same error. |
It looks like I had to do a couple things
I was then able to successfully run |
The GitHub action for Kubeflow triage is currently using the image
hamelsmu/kubeflow-triage
code-intelligence/.github/workflows/build_image.yaml
Line 15 in 9fceba0
code-intelligence/Issue_Triage/action/action.yml
Line 20 in 9fceba0
We should instead push the image to Docker in the kubeflow organization and then update the image to use that.
Note GitHub actions doesn't currently support GCR.
The text was updated successfully, but these errors were encountered: