Cannot start bitnami/sonarqube:latest (25.3.0) after upgrading from 25.2.0

[djaydjay31]

Name and Version

bitnami/sonarqube:latest (25.3.0)

What architecture are you using?

amd64

What steps will reproduce the bug?

I have a running server on image 25.2.0.

When I upgrade to last version (latest, 25.3.0) with the following docker compose:

services:
  sonarqube:
    # image: bitnami/sonarqube:25.2.0
    image: bitnami/sonarqube:latest
    restart: unless-stopped
    hostname: sonarqube.mydomain.com
    container_name: sonarqube
    depends_on:
      - db
    environment:
      - SONARQUBE_DATABASE_HOST=db
      - SONARQUBE_DATABASE_PORT_NUMBER=5432
      - SONARQUBE_DATABASE_USER=*******
      - SONARQUBE_DATABASE_PASSWORD=*********
      - SONARQUBE_DATABASE_NAME=sonar
    volumes:
      - /++++++++/sonarqube/sonarqube_data:/bitnami/sonarqube
    ports:
      - "127.0.0.1:9000:9000"
  db:
    image: bitnami/postgresql:15
    restart: unless-stopped
    hostname: postgres_sonar
    container_name: postgres_sonar
    environment:
      POSTGRES_USER: *********
      POSTGRES_PASSWORD: **********
      POSTGRES_DB: sonar
      POSTGRESQL_REPLICATION_USE_PASSFILE: null
    volumes:
      - /++++++++/sonarqube/pg:/bitnami/postgresql
      - /++++++++/sonarqube/pg_data:/bitnami/postgresql/data

After upgrading image version to 25.3.0,
I get:

fatal exception while booting Elasticsearch
sonarqube       | java.lang.IllegalStateException: Unable to access 'path.home' (/opt/bitnami/sonarqube/elasticsearch/plugins ...)
Elasticsearch is not starting. 

Isn't there some path error /opt/bitnami/sonarqube that should be /bitnami/sonarqube?
Regards

What is the expected behavior?

Sonarqube should start

What do you see instead?

Sonarqube is down

[jotamartos]

Sorry for the delay here. I just tried to reproduce the issue but couldn't do so. I launched a fresh Bitnami Sonarqube 25.2.0 image, and upgraded it to 25.3.0 after that. The container was started properly and I got the warning message regarding the migration of the database

sonarqube-1  | 2025.04.07 11:18:37 WARN  web[][o.s.s.p.DatabaseServerCompatibility] The database must be manually upgraded. Please backup the database and browse /setup. For more information: https://docs.sonarsource.com/sonarqube-community-build/server-upgrade-and-maintenance/upgrade/upgrade-the-server/roadmap
sonarqube-1  | 2025.04.07 11:18:37 WARN  app[][startup] ################################################################################
sonarqube-1  | 2025.04.07 11:18:37 WARN  app[][startup] The database must be manually upgraded. Please backup the database and browse /setup. For more information: https://docs.sonarsource.com/sonarqube-community-build/server-upgrade-and-maintenance/upgrade/upgrade-the-server/roadmap
sonarqube-1  | 2025.04.07 11:18:37 WARN  app[][startup] ################################################################################

I simply accessed the /setup endpoint and Sonarqube worked as expected after that

sonarqube-1  | 2025.04.07 11:20:51 INFO  ce[][o.s.c.c.ComputeEngineContainerImpl] Running Community edition
sonarqube-1  | 2025.04.07 11:20:51 INFO  ce[][o.s.ce.app.CeServer] Compute Engine is started
sonarqube-1  | 2025.04.07 11:20:51 INFO  app[][o.s.a.SchedulerImpl] Process[ce] is up
sonarqube-1  | 2025.04.07 11:20:51 INFO  app[][o.s.a.SchedulerImpl] SonarQube is operational

Please review if any plugin/extension is generating the error and check its forums/documentation to get more information.