Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

1.7 KiB

Docker Files for Windows Integration Tests

Index

About this File

In this file you will find which Dockerfiles are needed to run the Envoy integration tests on Windows, as well as information on how to run each of these files individually for testing purposes.

Pre-requisites

After building and running the images and containers, you need to have pre-built the base images used by these Dockerfiles. See pre-built images required in Windows

Dockerfile-test-sds-server-windows

This file sole purpose is to build the test-sds-server executable using Go. To do so, we use an official golang image provided in docker hub with Windows nano server. To build this image you need to run the following command on your terminal:

docker build -t test-sds-server -f Dockerfile-test-sds-server-windows test-sds-server

This is the same command used in run-tests.sh

You can test the built file by running the following command:

docker run --rm -p 1234:1234 --name test-sds-server test-sds-server

If everything works properly you should get the following output:

20XX-XX-XXTXX:XX:XX.XXX-XXX [INFO]  Loaded cert from file: name=ca-root
20XX-XX-XXTXX:XX:XX.XXX-XXX [INFO]  Loaded cert from file: name=foo.example.com
20XX-XX-XXTXX:XX:XX.XXX-XXX [INFO]  Loaded cert from file: name=wildcard.ingress.consul
20XX-XX-XXTXX:XX:XX.XXX-XXX [INFO]  Loaded cert from file: name=www.example.com
20XX-XX-XXTXX:XX:XX.XXX-XXX [INFO]  ==> SDS listening: addr=0.0.0.0:1234