title: Gitlab pull access denied for registry
body: <p>We migrated our old Ubuntu 16.04 Gitlab Server to a new Ubuntu 20.04.</p>
  <p>We running the gitlab image registry for our deployments. After the migration I have a strange problem, some user can no longer pull the image. The CI / CD Pipline is failing with the message:</p>
  <blockquote>
  <p>ERROR: Job failed: failed to pull image &quot;registry.domain.com/pathtoimage/image:version&quot; with specified policies [always]: Error response from daemon: pull access denied for registry.domain.com/pathtoimage/image, repository does not exist or may require 'docker login': denied: requested access to the resource is denied (manager.go:203:0s)</p>
  </blockquote>
  <p>On the other hand I an most of the other developers can run the Pipline without problem:</p>
  <blockquote>
  <p>Pulling docker image registry.domain.com/pathtoimage/image:version</p>
  </blockquote>
  <p>So I did some tests, if I am using the following commands on my local machine:</p>
  <pre><code>docker login registry.domain.com -u username
  </code></pre>
  <blockquote>
  <p>Login Succeeded</p>
  </blockquote>
  <pre><code>docker pull registry.domain.com/pathtoimage/image:version
  </code></pre>
  <blockquote>
  <p>Status: Downloaded newer image for registry.domain.com/pathtoimage/image:version</p>
  </blockquote>
  <p>But if the affected user is executing the same:</p>
  <pre><code>docker login registry.domain.com -u affected_username
  </code></pre>
  <blockquote>
  <p>Login Succeeded</p>
  </blockquote>
  <pre><code>docker pull registry.domain.com/pathtoimage/image:version
  </code></pre>
  <blockquote>
  <p>Error response from daemon: pull access denied for registry.domain.com/pathtoimage/image:version, repository does not exist or may require 'docker login': denied: requested access to the resource is denied</p>
  </blockquote>
  <p>So the user could login, but has no permission to pull the image, strange. How can I grant a user the permission for the Gitlab registry? Or how can I restore the permission for the affected users?</p>