Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Latest docker image bitbucket-server:8.1.1 fails to start (JRE_HOME not defined correctly)

Since I use the latest bitbucket-server:8.1.1 image, Bitbucket no longer starts. I get a JDK-related error message and the last commit ea5ff21fb3 ( is also related to a JDK change. Is that coincidence?

How to reproduce:

docker run --name="bitbucket" -d -p 7990:7990 -p 7999:7999 atlassian/bitbucket-server:8.1.1

That leads to these log entries (docker logs bitbucket):

INFO:root:Running Bitbucket with command '/opt/atlassian/bitbucket/bin/', arguments ['/opt/atlassian/bitbucket/bin/', '-fg']
The JRE_HOME environment variable is not defined correctly
This environment variable is needed to run this program
Edit and define JRE_HOME

Startup has been aborted


3 answers

It was explicitly written on docker hub bitbucket's page :facepalm
** Use docker version >= 20.10.9. **

Thank you, Ildar! Now I also found in on page, "Overview" section.

It works after Docker engine upgrade 20.10.4 -->20.10.17.

ReplyThis issue started after Atlassian pushed a new container image on the existing tag. which brock all container. i faced the same issue and also found the fix. (a workaround).
An image tag 7.19-jdk11 was pushed to the docker hub 7 months ago, and a day back same image was pushed with some changes, and that cause this issue.

REPOSITORY                 TAG        IMAGE ID     CREATED      SIZE
atlassian/bitbucket-server 7.19-jdk11 00485016b613 33 hours ago 1.2GB
atlassian/bitbucket-server <none> 555d7734717f 7 months ago 1.2GB

if you have the old working image already downloaded, tag it with some other name and start using it,

docker tag 555d7734717f atlassian/bitbucket-server:7.19.jdk11.working

Image ID: 555d7734717f is working well,
latest Image Id: 00485016b613 is not working


Update docker engine and new image will work

We also faced the same issue in 7.21.2 and found that in `` script the if-clause 

if [ -n "$JRE_HOME" ] && [[ -x "$JRE_HOME/bin/java" ]]; then

always negative due to [-x "$JRE_HOME/bin/java"] shows the binary is not executable, but it is 

And at the same time, a month ago 7.21.2 deployed well, but now we wanted to deploy it with different properties and faced this issue.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events