Problems with using pipes in a self hosted runner with deploying to beanstalk

David Bergevoet

I try to run the following pipeline:

This will cause the errors on bitbucket pipelines (docker: sed: write error). I dont know where this error comes from. It will work when i run this configuration on the bitbucket servers, by removing the runs-on keyword and variables. This will also deploy the right version to beanstalk.

Where does this error come from and how can i fix this? 

image: mcr.microsoft.com/dotnet/sdk:5.0

pipelines:
  pull-requests:
    "**":
      - step: test_pipeline
          runs-on:
            - 'self.hosted'
            - 'linux'
            - 'build'
          name: Test
          script:
            - pipe: atlassian/aws/elasticbeanstalk-deploy:1.0.2
              variables:
                AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID_DEV
                AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY_DEV
                AWS_DEFAULT_REGION: '<environment>'
                APPLICATION_NAME: '<name>'
                ENVIRONMENT_NAME: '<environment>'
                ZIP_FILE: '<some zip>'
                S3_BUCKET: 's3bucket>'
                WAIT: 'true'

 

 

[Edit] Other pipelines which dont need a pipe will run successful without problems

Norbert Csupka

Hi David,

Thank you for contacting Atlassian Support, my name is Norbert and I'm a Bitbucket Cloud Support Engineer, it's nice to meet with you! Welcome to the Atlassian Community! 

• Can you let me know whether the configuration that you posted, is that your full bitbucket-pipelines.yml file?
• Also, would it be possible for you to give us the runners logs from that timeperiod, when the build fails?

You can check the logs, by doing the following command on the host machine:

docker logs -f runner-runnerUUID 

 Please let us know, we're here to help.

Best Regards,
Norbert
Atlassian Bitbucket Cloud Support