Use oidc-user and oidc-token to run actions in a container
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 266
- Forks
- 110
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 3
Description
How can we help?
What is the expected way to run a github action in a container from an artifactory private registry using OIDC authentication? As far as I can tell the credentials need to be provided prior to any steps being executed and secrets can't be passed between jobs.
hello-from-container:
runs-on: ubuntu-latest
needs: login-via-oidc
container:
image: ${{ env.registry }}/ubuntu:latest
credentials:
username: "${{ needs.login-via-oidc.outputs.docker_user }}"
password: "${{ needs.login-via-oidc.outputs.docker_pass }}"
steps:
- name: hello
run: |
"echo hello"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides a GitHub Actions workflow using a private container image and OIDC-derived credentials, but names no repository file or test. Start by reviewing the workflow setup and existing authentication documentation; done means the supported way to run a container from a private Artifactory registry with OIDC is clearly documented or identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- authentication, ci-cd, devops
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100