You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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 (https://bitbucket.org/atlassian-docker/docker-atlassian-bitbucket-server/commits/) 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/start-bitbucket.sh', arguments ['/opt/atlassian/bitbucket/bin/start-bitbucket.sh', '-fg']
The JRE_HOME environment variable is not defined correctly
This environment variable is needed to run this program
Edit set-jre-home.sh and define JRE_HOME
Startup has been aborted
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