atlassian/bitbucket-mesh repository overview

Bitbucket Data Center is an on-premises source code management solution for Git that's secure, fast, and enterprise grade. Create and manage repositories, set up fine-grained permissions, and collaborate on code - all with the flexibility of your servers.

Bitbucket Mesh is an optional scalability extension for Bitbucket. For more information see https://confluence.atlassian.com/bitbucketserver/bitbucket-mesh-1128304351.html⁠.

⁠Overview

This Docker image is published as atlassian/bitbucket-mesh.

This Docker container makes it easy to get Mesh nodes for a Bitbucket Data Center up and running. It will only work in conjunction with a Bitbucket Data Center server.

For full documentation on running Bitbucket Data Center with Mesh nodes, see the Bitbucket documentation⁠.

** If running this image in a production environment, we strongly recommend you run this image using a specific version tag instead of latest. This is because the image referenced by the latest tag changes often and we cannot guarantee that it will be backwards compatible. **

** Use docker version >= 20.10.10 **

⁠Quick Start

For the MESH_HOME directory that is used to store the repository data (amongst other things) we recommend mounting a host directory as a data volume⁠, or via a named volume.

Volume permissions are managed by entry scripts. To get started you can use a data volume, or named volumes. In this example we'll use named volumes.

$> docker volume create --name bitbucketMeshVolume
$> docker run -v bitbucketMeshVolume:/var/atlassian/application-data/mesh --name="bitbucket-mesh" -d -p 7777:7777 atlassian/bitbucket-mesh

Note that this command can substitute folder paths with named volumes.

Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate both the application server and the git processes. See Supported Platforms⁠ for further information.

⁠Advanced Usage

For advanced usage, e.g. configuration, troubleshooting, supportability, etc., please check the Full Documentation⁠.