GeoNetwork is a catalog application to manage spatially referenced resources. It provides powerful metadata editing and search functions as well as an interactive web map viewer.
The GeoNetwork project started out in year 2001 as a Spatial Data Catalogue System for the Food and Agriculture organisation of the United Nations (FAO), the United Nations World Food Programme (WFP) and the United Nations Environmental Programme (UNEP).
At present the project is widely used as the basis of Spatial Data Infrastructures all around the world.
GeoNetwork has been developed to connect spatial information communities and their data using a modern architecture, which is at the same time powerful and low cost, based on the principles of Free and Open Source Software (FOSS) and International and Open Standards for services and protocols (e.g.: ISO/TC211, OGC).
The project is part of the Open Source Geospatial Foundation ( OSGeo ) and can be found at GeoNetwork opensource. GeoNetwork has been developed to connect spatial information communities and their data using a modern architecture, which is at the same time powerful and low cost.
%%LOGO%%
This command will start a debian-based container, running a Tomcat web server, with a geonetwork war deployed on the server:
$ docker run --name some-%%REPO%% -d %%IMAGE%%
Geonetwork listens on port 8080. If you want to access the container at the host, you must publish this port. For instance, this, will redirect all the container traffic on port 8080, to the same port on the host:
$ docker run --name some-%%REPO%% -d -p 8080:8080 %%IMAGE%%
Then, if you are running docker on Linux, you may access geonetwork at http://localhost:8080/geonetwork. Otherwise, replace localhost by the address of your docker machine.
The data directory is the location on the file system where the catalog stores much of its custom configuration and uploaded files. It is also where it stores a number of support files, used for various purposes (e.g.: Lucene index, spatial index, thumbnails).
By default, geonetwork sets the data directory on /usr/local/tomcat/webapps/geonetwork/WEB-INF/data, but you may override this value by injecting an environment variable into the container: - -e DATA_DIR=... (defaults to /usr/local/tomcat/webapps/geonetwork/WEB-INF/data)
For instance, to set the data directory to /var/lib/geonetwork_data:
$ docker run --name some-%%REPO%% -d -p 8080:8080 -e DATA_DIR=/var/lib/geonetwork_data %%IMAGE%%
If you want the data directory to live beyond restarts, or even destruction of the container, you can mount a directory from the docker engine's host into the container. - -v <host path>:<data directory>. For instance this, will mount the host directory /host/geonetwork-docker into /var/lib/geonetwork_data on the container:
$ docker run --name some-%%REPO%% -d -p 8080:8080 -e DATA_DIR=/var/lib/geonetwork_data -v /host/geonetwork-docker:/var/lib/geonetwork_data %%IMAGE%%
Run docker stack deploy -c stack.yml %%REPO%% (or docker-compose -f stack.yml up), wait for it to initialize completely, and visit http://swarm-ip:8080/geonetwork, http://localhost:8080/geonetwork, or http://host-ip:8080/geonetwork (as appropriate).
After installation a default user with name admin and password admin is created. Use this credentials to start with. It is recommended to update the default password after installation.