-
Notifications
You must be signed in to change notification settings - Fork 407
CloudBeaver Enterprise deployment from docker compose
Note: This deployment method is available in the Enterprise edition only.
- Overview
- Installation on Ubuntu
- Installation on macOS
- Installation on Windows
- Update CloudBeaver Enterprise
- Environment file configuration
- Docker Compose Variables
- CloudBeaver Configuration Variables
CloudBeaver Enterprise can be easily deployed using Docker Compose. This guide provides step-by-step instructions for setting up CloudBeaver Enterprise on Ubuntu, macOS, and Windows.
For advanced configurations, such as system requirements, ssl configuration, or podman requirements, refer to the Advanced settings guide.
Note: CloudBeaver Enterprise's Docker Compose setup includes a pre-configured web service.
- Ensure Docker and Docker Compose are installed by following the Docker installation guide for Linux.
- Install Docker Compose if it’s not already installed.
- Install Git if it’s not already installed.
-
Clone the deployment repository:
git clone https://github.com/dbeaver/cloudbeaver-deploy
-
Navigate to the CloudBeaver deploy directory:
cd cloudbeaver-deploy
-
Set up the
.env
file as described here.Important: You must change the default password in the
.env
file before starting the cluster. -
Start the cluster:
docker compose up -d
-
Access CloudBeaver Enterprise at
http://<server-ip>
.
Tip: Replace
<server-ip>
with your server’s actual IP address. You can configure the domain during the initial setup. For more details, see Domain Manager.
-
Install Docker Desktop for macOS from Docker website. Make sure Docker Desktop is running before proceeding.
-
Install Docker Compose if it’s not bundled with Docker Desktop:
brew install docker-compose
-
Install Git if it’s not already installed:
brew install git
-
Verify the installation:
docker --version docker-compose --version git --version
-
Clone the deployment repository:
git clone https://github.com/dbeaver/cloudbeaver-deploy
-
Navigate to the CloudBeaver deploy directory:
cd cloudbeaver-deploy
-
Set up the
.env
file as described here.Important: You must change the default password in the
.env
file before starting the cluster. -
Start the cluster:
docker-compose up -d
-
Access CloudBeaver Enterprise at
http://<server-ip>
.
Tip: Replace
<server-ip>
with your server’s actual IP address. You can configure the domain during the initial setup. For more details, see Domain Manager.
-
Install Docker Desktop for Windows from Docker website.
-
Install Git if it’s not already installed:
winget install --id Git.Git -e --source winget
-
Verify the installations:
docker --version docker-compose --version git --version
-
Clone the deployment repository:
git clone https://github.com/dbeaver/cloudbeaver-deploy
-
Navigate to the deployment directory:
cd cloudbeaver-deploy
-
Set up the
.env
file as described here.Important: You must change the default password in the
.env
file before starting the cluster. -
Start the cluster:
docker-compose up -d
-
Access CloudBeaver Enterprise at
http://<server-ip>
.
Tip: Replace
<server-ip>
with your server’s actual IP address. You can configure the domain during the initial setup. For more details, see Domain Manager.
For detailed update instructions, see Update version.
The .env
file provides configuration settings for CloudBeaver Enterprise. Below are key variables:
Variable | Description | Default value |
---|---|---|
IMAGE_SOURCE |
Defines the primary source of the Docker image. | dbeaver |
PODMAN_IMAGE_SOURCE |
Sets the Podman image source. | docker.io/dbeaver |
COMPOSE_PROJECT_NAME |
Defines the project name for Docker Compose. | dbeaver |
CLOUDBEAVER_VERSION_TAG |
Specifies the CloudBeaver version to use. See Docker tags. | 24.3.0 |
REPLICA_COUNT_EE |
Specifies the number of replicas for Enterprise Edition. See Docker Service Scale Documentation. | 1 |
Variable | Description | Default value |
---|---|---|
CLOUDBEAVER_WEB_SERVER_PORT |
Configures the web server port for CloudBeaver. | 8978 |
CLOUDBEAVER_DB_DRIVER |
Sets the database driver. See Server database for details. | postgres-jdbc |
CLOUDBEAVER_DB_URL |
Provides the database connection URL. | jdbc:postgresql://postgres:5432/cloudbeaver |
CLOUDBEAVER_DB_USER |
Sets the username for database authentication. | postgres |
CLOUDBEAVER_DB_PASSWORD |
Sets the password for database authentication. | You must change the default password in the .env file before starting the cluster. |
CLOUDBEAVER_DB_SCHEMA |
Defines the schema used in the CloudBeaver database. | cb |
CLOUDBEAVER_QM_DB_DRIVER |
Specifies the database driver for the Query Management (QM) system. | ${CLOUDBEAVER_DB_DRIVER} |
CLOUDBEAVER_QM_DB_URL |
Defines the connection URL for the QM database. | ${CLOUDBEAVER_DB_URL} |
CLOUDBEAVER_QM_DB_USER |
Sets the username for connecting to the QM database. | ${CLOUDBEAVER_DB_USER} |
CLOUDBEAVER_QM_DB_PASSWORD |
Sets the password for authenticating the QM database connection. | ${CLOUDBEAVER_DB_PASSWORD} |
CLOUDBEAVER_QM_DB_SCHEMA |
Defines the schema used in the QM database. | qm |
CLOUDBEAVER_DMSVC_URL |
Sets the URL of the Domain Manager service. | |
CLOUDBEAVER_RESTRICT_EXTERNAL_SERVICES_INVOCATION |
Blocks outbound calls to the License Manager. | true |
For more details on Server configuration, see Server configuration.
- Application overview
-
License Management
- Demo Server
- Supported databases
- Administration
- Server configuration
- Create Connection
- Network configuration settings
- Connection Templates Management
- Access Management
-
Authentication methods
-
Local Access Authentication
- Anonymous Access Configuration
- Reverse proxy header authentication
- LDAP
-
Single Sign On
-
SAML
-
OpenID
-
AWS OpenID
-
AWS SAML
-
AWS IAM
-
AWS OpenId via Okta
-
Snowflake SSO
-
Okta OpenId
-
Cognito OpenId
-
JWT authentication
-
Kerberos authentication
-
NTLM
-
Microsoft Entra ID authentication
-
Google authentication
-
Local Access Authentication
- User credentials storage
- Cloud databases configuration
-
Query Manager
-
Drivers Management
- Accessibility
- Keyboard shortcuts
- Features
- Server configuration
-
Domain manager
- Product configuration parameters
- Command line parameters
- Local Preferences
- API
- Deployment options
- Additional setup and management