Bitbucket Cloud: Resolving "Unable to find image '<workspace>/<repo>:latest' locally" Error When Pulling Custom Pipes Image
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
While accessing Bitbucket Pipes hosted on a Bitbucket repository, one may encounter the following pipe error:
1
"Unable to find image '<workspace>/<repo>:latest' locally. docker: Error response from daemon: pull access denied for <workspace>/<repo>, repository does not exist or may require 'docker login': denied: requested access to the resource is denied."Solution
There are two ways to refer to a pipe from other repositories. In bitbucket-pipelines.yml file, one can:
Refer to the Docker image directly: pipe: docker://acct/repo:tag (where acct/repo is the Dockerhub account and repo).
Note:
One must always specify docker:// when referencing public Docker images.
Refer to a pipe repo hosted on Bitbucket: pipe: <BB_acct>/repo:tag (where BB_acct/repo is your Bitbucket account and pipe repo).
When referring to a pipe hosted on Bitbucket Cloud, if the repository is set to private, you may encounter the error mentioned above. Please ensure that the repository is marked as public to successfully access the pipe from the pipelines. The pipe searches for the Docker image defined in the pipe.yml, which is hosted in the public pipe repository.
Was this helpful?