Are there any limitations on docker networking Bitbucket Pipelines?
I try the following in one of the steps:
When executed on my local machine, it prints the IP of the first container.
When executed in the pipeline, it produces non-zero exit code and crashes the pipeline. Changing version of docker image for the step (stable/latest) doesn't seem to have any effect.
I haven't run into any other issues with docker in pipelines yet.
Is this a known limitation of the Bitbucket Pipelines? Are there any workarounds?
Docker (networking) is limited within Bitbucket Pipelines. This is why you see it working on your local machine (docker is not limited there, you have full privileges) but failing on Bitbucket Pipelines.
As you have not shared the commands nor the errors it's hard to give more concrete directions.
The following article gives some more details about Docker networking on Atlassian Bitbucket Cloud in Pipelines:
Some more references, the first is a bit full of marketing but should nevertheless give a good overview and the scone is another Bitbucket blog post going into details on Docker and Docker Compose usage in pipelines. The third is a blog post by some hacker with a concrete setup comparing using local and Bitbucket Pipelines regarding Docker (in a docker compose setup):
Why Bitbucket Pipelines is the best CI/CD tool for your Docker-based software (May 2018 by Matt Ryall for Bitbucket)
Sibling Docker containers during BitBucket Pipelines - A Kafka use-case (Mar 2020 by Georgi Tenev for Dev.to)
HTH, if you still have the issue in concrete (your original posting is some weeks older), feel free to leave comments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.