Bitbucket has recently upgraded the bitbucket Pipeline infrastructure and upgraded the conatinerd version from 1.4.3 to containerd 1.5.0 starting August24th. Because of this, the pipleline build for S3 deployment from BB cloud is failing . It seems like "runc" has introduced a breaking change in its validation of the VOLUME mount path to ensure it's an absolute path and reject any relative path.
So an absolute path was suggested in the image and use that in the pipleline.
Here is the bitbucket-pipelines.yml code.
#########################################################
image: cgswong/aws:aws
pipelines:
branches:
master:
- step:
script:
- aws s3 ls s3://my-favourite-bucket/folder1/file1.txt
- echo "hello world"
- echo "Thank you very much !!"
######################################################
P.S Bitbucket suggests to update the image with the absolute path.
Bitbucket has recently upgraded the bitbucket Pipeline infrastructure and upgraded the conatinerd version from 1.4.3 to containerd 1.5.0 starting August24th. Because of this, the pipleline build for S3 deployment from BB cloud is failing . It seems like "runc" has introduced a breaking change in its validation of the VOLUME mount path to ensure it's an absolute path and reject any relative path.
So an absolute path was suggested in the image and use that in the pipleline.
Here is the bitbucket-pipelines.yml code.
#########################################################
image: cgswong/aws:aws
pipelines:
branches:
master:
- step:
script:
- aws s3 ls s3://my-favourite-bucket/folder1/file1.txt
- echo "hello world"
- echo "Thank you very much !!"
######################################################
P.S Bitbucket suggests to update the image with the absolute path.