Skip to content
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

Unable to start job with private images using circleci local execute #1033

Open
adoy opened this issue Jan 4, 2024 · 0 comments
Open

Unable to start job with private images using circleci local execute #1033

adoy opened this issue Jan 4, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@adoy
Copy link

adoy commented Jan 4, 2024

Meta:

CircleCI CLI Version:
0.1.29658+dd6a5b1

Operating System:
Linux debian 12.2

CircleCI CLI Diagnostic:

---
CircleCI CLI Diagnostics
---
Debugger mode: false
Config found: /home/pierrick/.circleci/cli.yml
API host: https://circleci.com
API endpoint: graphql-unstable
OK, got a token.
Trying an introspection query on API... 
Ok.
Hello, Pierrick Charron.


Current behavior:

I'm trying to run a job locally to test. The job is using an image that is on a private docker repo and the local execute command is unable to download it.

Starting container harbor.example.net/foo/bar:latest
  image cache not found on this host, downloading harbor.example.net/foo/bar:latest
Error: 
Error response from daemon: unauthorized: unauthorized to access repository: foo/bar, action: pull: unauthorized to access repository: foo/bar, action: pull

I tried to download it so that the image is already available but still not working :

Starting container harbor.example.net/foo/bar:latest                                                                                                                                                     
  image is cached as harbor.example.net/foo/bar:latest, but refreshing...                     
Error:                                                                                                     
Error response from daemon: unauthorized: unauthorized to access repository: foo/bar, action: pull: unauthorized to access repository: foo/bar, action: pull

Expected behavior:

I expect it to work using at least one of those solutions:

  • Use the ~/.docker/config.json to authenticate on the docker registry
  • Give an option to allow to log on the registry or to mount the docker/login.json
  • If the image is cached just use the one present.

When did this begin / Was this previously working?:

Never saw this working

Additional Information:

@adoy adoy added the bug Something isn't working label Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant