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

 <code>

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

    unittestcontainer$psql -h db_service - p5432

 </code>

 

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

<code>

    unittestcontainer$ # debug pipeline connection to database service.

    unittestcontainer$psql -h localhost - p5432

 </code>

 

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 Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

402 views 5 9
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