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
Describe the bug
Following this document, I want to launch a job on a container from my private ECR repository on self-hosted runner(dind mode in k8s).
However there is no basic auth credentials error from second job.
Pulling a private ECR image from login-to-ecr has no issue however pulling same image as a job container from CI-Test job got failed with Error response from daemon: Head "https://000000000000.dkr.ecr.ap-northeast-2.amazonaws.com/v2/actions-runner-image/manifests/latest": no basic auth credentials
To Reproduce
Steps to reproduce the behavior:
AWS private ECR login in first job and pass credentials as outputs to <job>.container.credentials to second job.
Expected behavior
A job on a container from private ECR repo should be launched on self-hosted runner.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
joosangkim
changed the title
Private ECR credentials are not passed from first job to second job/
Private ECR credentials are not passed from first job to second job
Jul 15, 2024
Describe the bug
Following this document, I want to launch a job on a container from my private ECR repository on self-hosted runner(dind mode in k8s).
However there is
no basic auth credentials
error from second job.action yaml
Pulling a private ECR image from
login-to-ecr
has no issue however pulling same image as a job container fromCI-Test
job got failed withError response from daemon: Head "https://000000000000.dkr.ecr.ap-northeast-2.amazonaws.com/v2/actions-runner-image/manifests/latest": no basic auth credentials
To Reproduce
Steps to reproduce the behavior:
<job>.container.credentials
to second job.Expected behavior
A job on a container from private ECR repo should be launched on self-hosted runner.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: