geonetwork / geonetwork/docker-geonetwork
Failed whilst adding the schema information in pre.xsd
- Dominant language
- Shell
- Stars
- 40
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
In order to ensure data permanence, i am used to sharing data between containers and docker host. With version 3.10.3, I was sharing in particular /config, and the docker composition was working fine.
but with version 4.0.1 and 4.0.2, I encounter an error when I share /catalog-data ...
Exception message if any is /catalogue-data/resources/xml/schemas/iso19115-3.2018/schema/standards.iso.org/19135/-2/pre/1.0/pre.xsd, Error=Raised exception while starting the application.
Fix the error and restart., Handler=org.fao.geonet.Geonetwork, Exception=OperationAbortedEx : Failed whilst adding the schema information.
Exception message if any is /catalogue-data/resources/xml/schemas/iso19115-3.2018/schema/standards.iso.org/19135/-2/pre/1.0/pre.xsd, Stack=OperationAbortedEx :
Failed whilst adding the schema information. Exception message if any is /catalogue-data/resources/xml/schemas/iso19115-3.2018/schema/standards.iso.org/19135/-2/pre/1.0/pre.xsd
below is an extract from my docker-compose.yml:
geonetwork:
image: geonetwork:4.0.2
...
volumes:
- /home/docker/docker-geonetwork/4.0.2/catalogue-data:/catalogue-data
# - geonetwork:/catalogue-data
The file pre.xsd does exist in the local folder, and it is fully read / write accessible.
$ pwd
/home/docker/docker-geonetwork/4.0.2
$ ls -l catalogue-data/resources/xml/schemas/iso19115-3.2018/schema/standards.iso.org/19135/-2/pre/1.0/pre.xsd
-rw-r--r-- 1 docker users 386 août 17 08:41 catalogue-data/resources/xml/schemas/iso19115-3.2018/schema/standards.iso.org/19135/-2/pre/1.0/pre.xsd
any help would be appreciated.
Ernest.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the volume mapping in docker-compose.yml and compare the mounted catalogue-data contents between GeoNetwork 3.10.3 and 4.0.1/4.0.2. Inspect the referenced pre.xsd path and the startup logs to identify why schema loading fails; done means the application starts successfully with /catalogue-data mounted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100