Not able to establish connection do DB with Docker

[philippfra]

Hello Community
I need help with my local Docker-setting.
To test CityGML-Files I would like to use 3DCityDB and Import/Export Tools in a local environment with Docker. I do the following:

1. set up a network: docker network create -d bridge citydb
2. Set up 3DCityDB: docker run --name cdb -p 5432:5432 -d --network=citydb -e POSTGRES_PASSWORD=tuttoPassi -e SRID=2056 -e HEIGHT_EPSG=5728 -e POSTGRES_DB=postgres -e POSTGRES_USER=postgres 3dcitydb/3dcitydb-pg
3. Import file: docker run -it --name impexp --rm --network=citydb -u $(id -u):$(id -g) -v ~/VCPublisher/VCdata:/data 3dcitydb/impexp import -d postgres -u postgres -p tuttoPassi -H cdb /data/private/3D_Gebaeude.gml
   I get the following Error:

[08:46:06 INFO] Starting 3D City Database Importer/Exporter, version 5.5.1
[08:46:06 INFO] Loading plugins
[08:46:06 INFO] Loading database schema mapping
[08:46:07 INFO] Loading ADE extensions
[08:46:07 INFO] Loading CityGML and ADE contexts
[08:46:07 INFO] Initializing application environment
[08:46:07 INFO] Executing 'import' command
[08:46:07 INFO] Connecting to database 'postgres@cdb:5432/postgres'.
[08:46:07 ERROR] Connection to database could not be established.
[08:46:07 ERROR] Caused by: java.sql.SQLException: No 3DCityDB instance found in given database schema 'citydb'.
[08:46:07 ERROR] Caused by: org.postgresql.util.PSQLException: The column name SCHEMA_SRID was not found in this ResultSet.
[08:46:07 WARN] Database import aborted.

With QGIS i can connect to the 3DCityDB (Host: 0.0.0.0, Port: 5432, Database: postgres). The DB here looks like follows:

Adding -e HEIGHT_EPSG=5728 to the DB-Container didn't change the Error. Without the docker-network, the Error said Connection refused. ... .
The file is valid according to docker run -it --name impexp --rm --network=citydb -u $(id -u):$(id -g) -v ~/VCPublisher/VCdata:/data 3dcitydb/impexp validate /data/private/3dcitydbtest/gebaeude3D.gml. The error stays the same, also with a non-existing file.

I tried to pull a different Image of the 3dCityDB, always the same Error. What am I missing?

[BWibo]

The error is possibly caused by a version mismatch between Importer/Exporter and 3DCityDB.
Check here to see what versions are compatible. https://docs.3dcitydb.net/compatibility/

From the screenshot you send, the database shema seems incomplete. There are some tables missing. Can you provide logs of the database container?

[philippfra]

Thanks for the hint. Got it working with: docker run --rm --network=citydb --name citydb-tool -e CITYDB_HOST=cdb -e CITYDB_PORRT=5432 -e CITYDB_NAME=postgres -e CITYDB_USERNAME=postgres -e CITYDB_PASSWORD=tuttoPassi -v ~/VCPublisher/VCdata/:/data 3dcitydb/citydb-tool import citygml /data/private/3D_Gebaeude.gml
The documentation here is probably misleading: https://3dcitydb-docs.readthedocs.io/en/latest/impexp/docker.html

[thomashkolbe]

The problem arises from the fact that you tried to use the new version of the 3DCityDB (V5) with the Importer/Exporter tool (impexp) for the old version 3DCityDB V4. You need to use a consistent combination. These are explained in the new documentation: https://docs.3dcitydb.net/compatibility/

[philippfra]

Sure. But if I follow the steps in the old documentation, its not working because I got a new db an an old tool. It would be helpful if there were a hint to the new tool an this link in the documentation.

[clausnagel]

The old documentation already states the supported versions clearly: https://3dcitydb-docs.readthedocs.io/en/version-2024.0/

To make things clearer, I’ve updated the Importer/Exporter to throw an explicit error message when attempting to connect to a 3DCityDB v5 database. This should help users avoid confusion in the future. The fix is included in the Docker images 5.5.2, latest, and edge of the Importer/Exporter.

[clausnagel]

We have added a more descriptive error message to the Importer/Exporter (see answer above) and placed a banner on the old documentation (thanks to @BWibo for this contribution). The situation should now be sufficiently clear, so closing this thread.