You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey all 👋
I have spent a considerable amount of time trying to find a solution for the following problem:
We want to run a job inside a container where the container lives in Google Artifact Registry (GAR). What we do in order to authenticate against our private registry is OIDC. Here's the code:
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDQuestion
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey all 👋
I have spent a considerable amount of time trying to find a solution for the following problem:
We want to run a job inside a container where the container lives in Google Artifact Registry (GAR). What we do in order to authenticate against our private registry is OIDC. Here's the code:
which essentially uses
docker/login-action
to authenticate to GAR and then exports the creds to an output variable.Then my next job is:
The problem I face is that when the first job is done, as a last step I get:
and so the
password
field in therun_container
job is empty. I have tried the same with:but doesn't work either - github still doesn't let me pass this from the first job to the second one.
Questions:
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions