Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

BitBucket's Docker container IP is not properly linking Bamboo CI IP

Hi Everyone

I have successfully spawned a container out of Atlassian's Bitbucket image. I am able to access it through http://<container-ip>:7990. I have also installed Bamboo CI on my Ubuntu VM. It has also started successfully.

I am able to access Bamboo CI through a static IP configured for the aforementioned ubuntu vm (http://<static-ip>:8085). But the problem is coming up while linking these two applications.

As aforementioned, I am getting the following error:

Application link bitbucket was created successfully but the reciprocal link wasn't created successfully.

The peculiar aspect is, the bamboo IP is automatically resolving to when I am trying to link it with Bitbucket. This shouldn't happen. Bamboo should link with Bitbucket using its static-ip.

Has anyone encountered this problem and resolved it?



1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 02, 2018

>the bamboo IP is automatically resolving to

Check that the base url is set correctly (on both sides) and that the network is routing <static-ip> to the right place.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events