-
Notifications
You must be signed in to change notification settings - Fork 15
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
[BUG] (Self-hosted arm64 runner) Error: Error: ENOENT: no such file or directory, open '/tmp/podman-run-0/containers/auth.json' #41
Comments
I ran into this issue on a similar host and found this to work when running as root in the buildah container, added to
|
Tried that as well. Fails with:
The workflow: https://github.com/yuravk/bootc-images/actions/runs/10244618540/job/28337995308 |
I reported an issue on that error to (#42 ), my current workaround there is to use a local custom buildah container that includes this line from (#39 )
Then I use that container as the runner instead of the upstream buildah stable image on quay |
Version
redhat-actions/podman-login@v1
Describe the bug
The action fails on self-hosted runner because of the error:
However log in to quay.io succeed.
Steps to reproduce, workflow links, screenshots
The action runs on AlmaLinux (Red Hat binary compatible OS) arm64 based self-hosted runner:
The workflow raw log:
The workflow link:
https://github.com/yuravk/bootc-images/actions/runs/10201571885/job/28223790588#step:4:25
The text was updated successfully, but these errors were encountered: