Bitbucket Cloud: Resolving "Unable to find image '<workspace>/<repo>:latest' locally" Error When Pulling Custom Pipes Image

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Cloud のみ - この記事は、 クラウド プラットフォームのアトラシアン製品にのみ適用されます。

    

要約

While accessing Bitbucket Pipes hosted on a Bitbucket repository, one may encounter the following pipe error:

"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."


ソリューション

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).

    注意:

    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.

最終更新日: 2024 年 1 月 26 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.