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

Error response from daemon: pull access denied for ubuntu-2004 #72

Open
kienstra opened this issue Jan 6, 2022 · 5 comments
Open

Error response from daemon: pull access denied for ubuntu-2004 #72

kienstra opened this issue Jan 6, 2022 · 5 comments

Comments

@kienstra
Copy link
Member

kienstra commented Jan 6, 2022

With a config like this:

jobs:
  e2e-build:
    machine:
      image: ubuntu-2004:202111-02
    steps:
      - checkout

There's an error like:

Unable to find image 'ubuntu-2004:202111-02' locally
docker: Error response from daemon: pull access denied for ubuntu-2004, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.

This happens with several ubuntu-* images.

Maybe logging into Docker is needed.

@aronchick
Copy link

+1 - seeing the same with the following:

  ubuntu-amd64:
    machine:
      image: ubuntu-2204:2022.04.2
    resource_class: xlarge
====>> Spin up environment
Build-agent version  ()
System information:
 Server Version: 20.10.14
 Storage Driver: overlay2
  Backing Filesystem: extfs
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Kernel Version: 5.10.104-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64

Starting container ubuntu-2204:2022.04.2
Warning: No authentication provided, using CircleCI credentials for pulls from Docker Hub.
  image cache not found on this host, downloading ubuntu-2204:2022.04.2

  Error pulling image ubuntu-2204:2022.04.2: Error response from daemon: pull access denied for ubuntu-2204, repository does not exist or may require 'docker login': denied: requested access to the resource is denied... retrying
  image cache not found on this host, downloading ubuntu-2204:2022.04.2

  Error pulling image ubuntu-2204:2022.04.2: Error response from daemon: pull access denied for ubuntu-2204, repository does not exist or may require 'docker login': denied: requested access to the resource is denied... retrying
  image cache not found on this host, downloading ubuntu-2204:2022.04.2

  Error pulling image ubuntu-2204:2022.04.2: Error response from daemon: pull access denied for ubuntu-2204, repository does not exist or may require 'docker login': denied: requested access to the resource is denied... retrying
  image cache not found on this host, downloading ubuntu-2204:2022.04.2

  Error pulling image ubuntu-2204:2022.04.2: Error response from daemon: pull access denied for ubuntu-2204, repository does not exist or may require 'docker login': denied: requested access to the resource is denied... retrying
  image cache not found on this host, downloading ubuntu-2204:2022.04.2

  Error pulling image ubuntu-2204:2022.04.2: Error response from daemon: pull access denied for ubuntu-2204, repository does not exist or may require 'docker login': denied: requested access to the resource is denied... retrying
  image cache not found on this host, downloading ubuntu-2204:2022.04.2
Error: 
Error response from daemon: pull access denied for ubuntu-2204, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Step failed
Task failed
Error: Error response from daemon: pull access denied for ubuntu-2204, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
  ~/code/bacalhau   circleci-project-setup ⇡45 *1       

I am logged in via docker though

@kienstra
Copy link
Member Author

kienstra commented Jul 2, 2022

Hi @aronchick,
Thanks a lot for letting me know about that.

It looks like that'll depend on an upstream issue: CircleCI-Public/circleci-cli#671

The CLI doesn't support machine executors.

Sorry, I should have mentioned that in the Local CI docs or marketing.

I know machine executors are important, as that's where a lot of e2e tests run.

Thanks so much for using Local CI, sorry about machine executors not working in it.

@kienstra
Copy link
Member Author

kienstra commented Jul 2, 2022

You're probably running a machine executor for a good reason.

But if by chance you could get away with a docker executor, Local CI should work for that.

You're probably really experienced with CircleCI if you're using Local CI 😄

@aronchick
Copy link

Totally understood - the issue is that I do need a machine executor because i need to run containers as part of my job (so unless i can do docker in docker, i'm stuck)

@kienstra
Copy link
Member Author

kienstra commented Jul 3, 2022

Sure, that makes sense that you'd need it to run containers for your job. I'm advocating that they consider the upstream issue, though it sounds like a hard one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants