Are there any limitations on docker networking Bitbucket Pipelines?
I try the following in one of the steps:
- Create a bridge network `somenet`
- Start a container with a set name `onecontainer` and specify that it should be connected to `somenet` via `--network somenet`
- Start the second container connected to the same network and attempt to resolve first containers name by passing `getent hosts onecontainer` as a command.
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?