Pipeline crashes on cloning step (build setup)

[Martijn van de Wetering]

Hi community,

While trying to use a private image from AWS ECR, the pipeline keeps crashing on the step:

Cloning into '/opt/atlassian/pipelines/agent/build'...

Authentication works, I have both tried the OIDC and Access key approach. Which have given me authorization errors that have been fixed. The 'pulling images' step successfully completes.

To ensure it is not a fault in the image, I have tagged and pushed the atlassian/default-image:4 to the private ECR repo. Which is the image I am using now.

Is this a known error? or what could cause this?

Error:

Pipeline:

image:
  name: 12345678910.dkr.ecr.eu-central-1.amazonaws.com/repo/image:tag
  aws:
    access-key: $AWS_ACCESS_KEY
    secret-key: $AWS_SECRET_KEY

clone:
  depth: full

definitions:
  services:
    docker:
      memory: 2048
      type: docker

  steps:
    - step: &composer-install
        name: Install dependencies
        caches:
          - composer
        script:
          - composer --version
          - composer install --no-interaction --prefer-dist --optimize-autoloader --no-dev
        artifacts:
          - vendor/**
          - composer.lock

[Theodora Boudale]

Hi Martijn and welcome to the community!

I don't see any obvious reason why this step would fail.

I see that the image definition is a global one. Is the same image used as a build container in the other (successful) parallel step, named "Compile assets"?

You could also try defining a public DockerHub image for the failed step (on the step level), temporarily, for testing purposes, to better understand if the issue seems to be related to the ECR image definition or not. You can do it by adjusting the step as follows:

- step: &composer-install
    name: Install dependencies
    image: composer:latest
    caches:
      - composer
    script:
      - composer --version
      - composer install --no-interaction --prefer-dist --optimize-autoloader --no-dev
    artifacts:
      - vendor/**
      - composer.lock

I also recommend creating a ticket with the support team for further investigation. If we have a support ticket, we'll be able to check additional logs on our side to better understand what is happening.

You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation.

Please make sure you provide the URL of a failed build in the ticket, for further investigation. A support ticket you create can be accessed only by you, Atlassian staff, and any other users you may add as participants, so anything you post there won't be publicly visible.

Kind regards,
Theodora