Some odd container register behaviour

I have two projects under the same folder tree see below

company
|
+---- Folder
            |
            +---- Container registry
            |
            +---- Folder 1
            |            |
            |            +---- Project 1
            |
            +---- Folder 2
                         |
                         +---- Project 2

Project 1 and 2 both use the same image reference and the same runner
image: ${CI_REGISTRY}/company/Folder/containers/ci-container-testing/imagename:v0.1

Project 1 works correctly
Project 2 fails with a container registry auth error.

Running in runner-9597414-project-28807693-concurrent-0-1523536894
Login to registry.gitlab.com with CI_DEPLOY_USER
Login Succeeded!
gitlab+deploy-token-540177
gitlab+deploy-token-540177
Trying to pull registry.gitlab.com/company/Folder/containers/ci-container-testing/imagename:v0.1...
  denied: requested access to the resource is denied
Error: Error initializing source docker://registry.gitlab.com/company/Folder/containers/ci-container-testing/imagename:v0.1: Error reading manifest v0.1 in registry.gitlab.com/company/Folder/containers/ci-container-testing/imagename: errors:
denied: requested access to the resource is denied
unauthorized: authentication required
ERROR: Preparation failed: exit status 2

I can’t find anywhere to manage the auth for the registry that is any different for either project, project 2 .gitlab-ci.yml is literally a copy of the one in project 1.
Really stuck at this point.

Describe your question in as much detail as possible:

  • What are you seeing, and how does that differ from what you expect to see?

  • Consider including screenshots, error messages, and/or other helpful visuals

  • What version are you on? Are you using self-managed or GitLab.com?

    • GitLab (Hint: /help):
    • Runner (Hint: /admin/runners):
  • Add the CI configuration from .gitlab-ci.yml and other configuration if relevant (e.g. docker-compose.yml)

  • What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

Thanks for taking the time to be thorough in your request, it really helps! :blush:

This turned out to be an issue with cached credentials for git, I cleared them globally and recloned the repo, all good