Kubernetes_Cannot run program "pg_dump" when upgrading cloudbeaver-ce from 25.2.1 to 25.2.2

[nickramos94]

Description

Hi everyone,

I have tried to upgrade our Cloudbeaver-ce that we are running on Red Hat Openshift for testing purposes from v25.2.1 to v25.2.2 but the main container fails to load because it can't manage to perform the backup of its database. The previous version had been running fine with no issues.

... 16-10-2025 09:36:39.151 [main] DEBUG i.c.service.security.db.CBDatabase - Initiate connection pool with management database (PostgreSQL; jdbc:postgresql://postgres:5432/cloudbeaver) 16-10-2025 09:36:39.346 [main] INFO o.j.d.e.p.b.JDBCDatabasePostgresBackupHandler - Command started: pg_dump cloudbeaver --host postgres --port 5432 --blobs --verbose --file /opt/cloudbeaver/workspace/backup/cloudbeaver_backup_version_cb25.zip --schema cb 16-10-2025 09:36:39.348 [main] ERROR o.j.d.e.p.b.JDBCDatabasePostgresBackupHandler - Create backup is failed: Cannot run program "pg_dump": error=2, No such file or directory 16-10-2025 09:36:39.348 [main] WARN o.j.d.m.sql.schema.SQLSchemaManager - CB_CE migration has been rolled back 16-10-2025 09:36:39.349 [main] ERROR io.cloudbeaver.server.CBApplication - Error initializing database org.jkiss.dbeaver.DBException: Error updating management database schema ....

I imagine that the pg_dump is already present in the cloudbeaver:25.2.2 image.

Steps to reproduce

1. I have set the imageTag variable value as "25.2.2" in the values.yaml file of Cloudbeaver's Helm chart
2. Pushed the new chart to OpenShift
3. The previous container gets deleted and the updated one gets created but fails to start

Here is the container's log
cloudbeaver.log

Expected/Desired Behavior

For Cloudbeaver to start normally

CloudBeaver Version

25.2.1

Additional context

Red Hat Openshift 4.19.13

[dariamarutkina]

Hello, @nickramos94 !
Thank you for the issue! 🦫

It looks like your system lacks the PostgreSQL client tools (pg_dump). Please install them on your system.

We’ll update the documentation to clarify this.

[nickramos94]

Hi @dariamarutkina, thanks for you answer.

It looks like your system lacks the PostgreSQL client tools (pg_dump). Please install them on your system.

My "system" is the container that is officially provided by Cloudbeaver that I left untouched, if there is the need of performing a backup of the DB before an upgrade I reckon that you (as a company) might:

1. include pgdump in the Cloudbeaver's image so that it can perform the backup
2. leave the backup duties to the administrator (like I am already doing) and remove the backup step from the container's update process

Anyway I'm seeing that a similar problem was already addressed here with a workaround that disables the backup step, but I believe that is more a matter of how the container is built by Cloudbeaver rather than a simple documentation issue.

After disabling the backup from Cloudbeaver's configuration files the update completed successfully.