"Built for professional teams - Distributed version control system that makes it easy for you to collaborate with your team. The only collaborative Git solution that massively scales." - [Source]
| Product | Version | Tags | Dockerfile |
|---|---|---|---|
| Bitbucket | 4.14.4 | 4.14.4, latest | Dockerfile |
You may also like:
- blacklabelops/jira: The #1 software development tool used by agile teams
- blacklabelops/confluence: Create, organize, and discuss work with your team
- blacklabelops/bitbucket: Code, Manage, Collaborate
- blacklabelops/crowd: Identity management for web apps
Docker-CLI:
Just type and follow the manual installation procedure in your browser:
$ docker run -d -p 7990:7990 --name bitbucket blacklabelops/bitbucket
Point your browser to http://yourdockerhost:7990
- Start database server for Bitbucket.
- Start Bitbucket.
- Manual Bitbucket setup.
Firstly, start the database server for Bitbucket:
Note: Change Password!
$ docker run --name postgres_bitbucket -d \
-e 'POSTGRES_DB=bitbucketdb' \
-e 'POSTGRES_USER=bitbucketdb' \
-e 'POSTGRES_PASSWORD=jellyfish' \
-e 'POSTGRES_ENCODING=UTF8' \
blacklabelops/postgres
Secondly, start Bitbucket:
$ docker run -d --name bitbucket \
--link postgres_bitbucket:postgres_bitbucket \
-p 7990:7990 blacklabelops/bitbucket
Starts Crowd and links it to the postgresql instances. JDBC URL: jdbc:postgresql://postgres_bitbucket/bitbucketdb
Thirdly, configure your Bitbucket yourself and fill it with a test license.
Point your browser to http://yourdockerhost:7990
- Choose
ExternalforDatabaseand fill out the form:
- Database Type:
PostgreSQL - Hostname:
postgres_bitbucket - Port:
5432 - Database name:
bitbucketdb - Database username:
bitbucketdb - Database password:
jellyfish
- Create and enter license information
- Fill out the rest of the installation procedure.
If you need to use SSH Keys to authenticate Bitbucket to other services (eg, replicating to Github), put the entire contents of what you want to have in the .ssh directory in a directory called 'ssh' on your persistant volume.
When the container is started, the contents of /var/atlassian/bitbucket/ssh directory will be copied to /home/bitbucket/.ssh, and the permissions will be set to 700.
Example:
$ docker run -d --name bitbucket \
-v your-local-ssh-folder-or-volume:/var/atlassian/bitbucket/ssh \
-e "BITBUCKET_PROXY_NAME=myhost.example.com" \
-e "BITBUCKET_PROXY_PORT=443" \
-e "BITBUCKET_PROXY_SCHEME=https" \
blacklabelops/bitbucket
ssh keys will be copied and are available at runtime.
Alternatively copy the files in your running container and restart the container:
# Creating the folder
$ docker exec bitbucket mkdir -p /var/atlassian/bitbucket/ssh
# Copy the keys
$ docker cp your-local-ssh-folder your-container-name:/var/atlassian/bitbucket/ssh
# Restart container
$ docker restart your-container-name
You can specify your proxy host and proxy port with the environment variables BITBUCKET_PROXY_NAME and BITBUCKET_PROXY_PORT. The value will be set inside the Atlassian server.xml at startup!
When you use https then you also have to include the environment variable BITBUCKET_PROXY_SCHEME.
Example HTTPS:
- Proxy Name: myhost.example.com
- Proxy Port: 443
- Poxy Protocol Scheme: https
Just type:
$ docker run -d --name bitbucket \
-e "BITBUCKET_PROXY_NAME=myhost.example.com" \
-e "BITBUCKET_PROXY_PORT=443" \
-e "BITBUCKET_PROXY_SCHEME=https" \
blacklabelops/bitbucket
Will set the values inside the server.xml in /opt/bitbucket/.../server.xml
This is an example on running Atlassian Bitbucket behind NGINX with 2 Docker commands!
First start Bitbucket:
$ docker run -d --name bitbucket \
-e "BITBUCKET_PROXY_NAME=192.168.99.100" \
-e "BITBUCKET_PROXY_PORT=80" \
-e "BITBUCKET_PROXY_SCHEME=http" \
blacklabelops/bitbucket
Example with dockertools
Then start NGINX:
$ docker run -d \
-p 80:80 \
--name nginx \
--link bitbucket:bitbucket \
-e "SERVER1REVERSE_PROXY_LOCATION1=/" \
-e "SERVER1REVERSE_PROXY_PASS1=http://bitbucket:7990" \
blacklabelops/nginx
Bitbucket will be available at http://192.168.99.100.
This is an example on running Atlassian Bitbucket behind NGINX-HTTPS with2 Docker commands!
Note: This is a self-signed certificate! Trusted certificates by letsencrypt are supported. Documentation can be found here: blacklabelops/nginx
First start Bitbucket:
$ docker run -d --name bitbucket \
-e "BITBUCKET_PROXY_NAME=192.168.99.100" \
-e "BITBUCKET_PROXY_PORT=80" \
-e "BITBUCKET_PROXY_SCHEME=http" \
blacklabelops/bitbucket
Example with dockertools
Then start NGINX:
$ docker run -d \
-p 443:443 \
--name nginx \
--link bitbucket:bitbucket \
-e "SERVER1REVERSE_PROXY_LOCATION1=/" \
-e "SERVER1REVERSE_PROXY_PASS1=http://bitbucket:7990" \
-e "SERVER1CERTIFICATE_DNAME=/CN=CrustyClown/OU=SpringfieldEntertainment/O=crusty.springfield.com/L=Springfield/C=US" \
-e "SERVER1HTTPS_ENABLED=true" \
-e "SERVER1HTTP_ENABLED=false" \
blacklabelops/nginx
Bitbucket will be available at https://192.168.99.100.
First install:
Vagrant is fabulous tool for pulling and spinning up virtual machines like docker with containers. I can configure my development and test environment and simply pull it online. And so can you! Install Vagrant and Virtualbox and spin it up. Change into the project folder and build the project on the spot!
$ vagrant up
$ vagrant ssh
[vagrant@localhost ~]$ cd /vagrant
[vagrant@localhost ~]$ docker-compose up
Bitbucket will be available on http://localhost:8080 on the host machine.
Leave a message and ask questions on Hipchat: blacklabelops/hipchat