"Pull access denied" error when building in the cloud

Product support balenaEngine
1

I’m getting the following error. The dockerhub account works and there should be no problem logging in. I checked the password provided in the registry-secrets.yml file and it is the correct one. This error started to appear today.

[Info]         Starting build for Telemetry_Prod_Hologram, user ***
[Info]         Dashboard link: https://dashboard.balena-cloud.com/apps/***
[Info]         Building on arm01
[Info]         Pulling previous images for caching purposes...
[Success]      Successfully pulled cache images
[receiver]     Step 1/5 : FROM mwolleben/telemetry:receiver-1.0
[watchdog]     Step 1/7 : FROM mwolleben/telemetry:watchdog-1.0
[dashboard]    Step 1/18 : FROM mwolleben/telemetry:dashboard-1.0
[folderwatch]  Step 1/5 : FROM mwolleben/telemetry:folderwatch-1.0
[networking]   Step 1/18 : FROM mwolleben/telemetry:networking-1.0
[watchdog]     pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[dashboard]    pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[receiver]     pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[folderwatch]  pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[networking]   pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[powermgmt]    Step 1/4 : FROM mwolleben/telemetry:powermgmt-1.0
[powermgmt]    pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[Error]        Some services failed to build:
[Error]          Service: networking
[Error]            Error: pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[Error]          Service: dashboard
[Error]            Error: pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[Error]          Service: receiver
[Error]            Error: pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[Error]          Service: watchdog
[Error]            Error: pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[Error]          Service: folderwatch
[Error]            Error: pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[Error]          Service: powermgmt
[Error]            Error: pull access denied for mwolleben/telemetry, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[Info]         Built on arm01
[Error]        Not deploying release.
6

Hi Maik, thank you for reporting this issue. We are investigating whether it might be related to a balenaCloud builder deployment earlier today. Would you be able to check and share the URL that you are using in the registry-secrets.yml file? Does it happen to be “https://index.docker.io/v1/”? Paulo

7

This is the registry-secrets.yml file:

'':  # Use the empty string to refer to the Docker Hub
    username: ********
    password: ********
9

Thank you for sharing it. We are investigating the issue and will report back to you soon.

10

We’re having the same issue, it worked fine 2 days ago and we’re in a rush to deploy a fix at customer site.

11

Hi there – we have just reverted a change to our build infrastructure, and that should resolve this problem. Can you please try this and let us know if your build now works?

Thanks,
Hugh

12

[Error] Error: pull access denied for rapid****/***_service, repository does not exist or may require ‘docker login’

Still the same

13

Thank you for the update, @jayv, we’re checking into this.

14

Hi @jayv – as I write this, it’s more than 45 minutes after initiating the rollback, and you should not be hitting any of the old, problematic builder instances anymore. Those instances are left up to complete any builds in progress, rather than disruptiing them, but any new connections go to the new, fixed instances.
If you are still hitting this problem:

  • Are you able to try rebooting your machine? We want to make sure that there is no lingering connection to the builder that may be in play.
  • If it continues to fail, can you please post the full command being run, the application numerical ID, and the output of the build? Please redact anything sensitive, but we will need the info to track things down on our end.

Thanks,
Hugh

1 Like
15

Are you able to try rebooting your machine? We want to make sure that there is no lingering connection to the builder that may be in play.

balena push .... runs from a Github Action container, so there is no way a process or connection to balena cloud remains up.

if it continues to fail, can you please post the full command being run, the application numerical ID, and the output of the build?

It did right after the reported fix, but it seems to be working now

16

Glad to hear it @jayv – thanks, and please let us know if you run into any further problems.

All the best,
Hugh

17

It’s working for me too now. Thanks!