-
Notifications
You must be signed in to change notification settings - Fork 0
Docker deployment using local docker compose files
Use this approach to deploy when you have access to the machine you're trying to run the containers on
- AWS CLI tool v2 (see https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html) for authenticating with AWS Public Elastic Container Registry
- Docker and docker-compose
- This repository cloned as
os-custom-geonetwork
- The repositories https://github.com/AstunTechnology/iso19139.gemini23 (3.10.x branch) and https://github.com/AstunTechnology/iso19139.gemini22_GN3 (3.8.x branch) cloned as
iso19139.gemini23
andiso19139.gemini22_GN3
respectively.
Your directory structure should look like this:
/somewhere/os-custom-geonetwork
/somewhere/iso19139.gemini23
/somewhere/iso19139.gemini22_GN3
Change to the os-custom-geonetwork/docker
directory and make a copy of .env-local.sample
as env-local
and fill in the password you'd like to use for the geonetwork user in the database.
The same password should be used for both environment variables. Do not add this file to version control or otherwise publish it
Authenticate with AWS ECR (note use the below command exactly as it is):
aws ecr-public get-login-password --region us-east-1 | docker login --username AWS --password-stdin public.ecr.aws
The following command will run docker in quiet mode, eg you won't see any logs or errors on the command line. To see logs etc, omit the -d
parameter
docker-compose -f docker-compose.yml -f up -d
To see logs when running docker in quiet mode, run the following in a new command window:
docker-compose logs --follow
GeoNetwork will be available at http://localhost:81/geonetwork