Skip to main content

Version v2021.0 (18/01/2021) v2021.0 Switch to the latest release

Published on: 03/02/2021 Last update: 10/03/2023

Version summary

The version published at this time contains breaking and non-breaking changes.

New Features




  • #324 Added a validation when parent Authority url is not defined - #549
  • #338 Temporal filter errors in Conformance Class: Download Service - Direct WFS Team Engine
  • #346 Improved information on docker deployment
  • #389 Updated features in PLU - #512
  • #397 Added manual check on nz-as - #529
  • #422 WMS executed tests are not found in the list of tests executed by the validator
  • #424 Added date validation for data consistency - #532

Deployment instructions

Section containing deployment process using Docker image and troubleshooting section. You can also find these in the training materal

As a prerrequisite to use the Docker packages from GitHub, you would need to create an access token as a way to authenticate on the registry. You can get more information here

docker login 
#Provide Github credentials
docker run --name inspire-validator -d -p 8080:8080 -v ~/etf:/etf
#Launches a container with the image, exposing it port 8080 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf

Modifying the Docker image

In the inspire-validator ZIP file you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8080:8080 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on the production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to acces their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/, and modify the etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually host machines are connected in a private network that access to the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out

For further configuration, please download the file and follow the instructions in the file inside the .zip file.

Find changelog details & deployment instructions:

Assets contained in this release: