How to debug pipeline service containers Edited

I'm using docker-compose (2.1) locally to bring up my unit testing container with depends_on a database service and samba service. Under docker-compose, the depends_on services come up on a bridged hostname that matches the service name, i.e


    unittestcontainer$ # debug docker-compose connection to database service.

    unittestcontainer$psql -h db_service - p5432



Under bitbucket pipeline builds, the services are available on the main container ie.


    unittestcontainer$ # debug pipeline connection to database service.

    unittestcontainer$psql -h localhost - p5432



The difference between services on a localhost or remote hostname is causing a lot of friction, with tests that depend on samba service. Is there a better way to locally debug interactions with service containers ?


0 answers

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

624 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot