Dockerized GeoServer micro-services
Docker images for all the services are available on DockerHub, under the geoservercloud organization.
Starting with version 1.8.6
, all Docker images are signed with cosign.
In order to verify the signatures, install cosign,download the cosign.pub file containing the public key, and run
cosign verify --key cosign.pub geoservercloud/<image name>:1.8.6
The public key can also be an environment variable. For example:
export GSC_COSIGN_PUB_KEY=`cat cosign.pub`
cosign verify --key env://GSC_COSIGN_PUB_KEY geoservercloud/<image name>:1.8.6
In any case, replace
1.8.6
with the specific version you’re using
Usually you’d only use the config service in Docker Compose deployments. In a Kubernetes environment, we prefer to use the externalized configuration embedded in the Docker images under
/etc/geoserver/
and Kubernetes ConfigMaps or Secrets.
This service is primarily used in Docker Compose deployments. For Kubernetes deployments, it’s recommended to use the
standalone
Spring profile and rely on Kubernetes Services for service discovery and load balancing.
Please check out the docker-compose deployment document.
Please check out the example Helm chart on this helm-geoserver-cloud repository as a starting point to deploy to K8s.
Follow the Podman’s deployment guide to use Podman’s daemonless container engine for Cloud Native GeoServer containers.