tia® Proxy (Container)
The tia® Proxy is based on the OSGi-Framework. Since version 2.0.2 the tia® Proxy is available as a container.
Snippet Summary
docker login https://images.kgs-cloud.de
docker pull images.kgs-cloud.de/tia-proxy/tia-proxy:<version>
docker run --name proxy -p 8080:8080 -v {YOUR HOST DIRECTORY MOUNT PATH}:/application/work -d images.kgs-cloud.de/tia-proxy/tia-proxy:<version>Step 1: Pull the Image
docker pull images.kgs-cloud.de/tia-proxy/tia-proxy:<version>Step 2: Start with mount options
It is necessary to mount a filesystem path into the container in order to persist the product (KGS Proxy) configuration. This procedure ensures that the configuration is not lost after a restart/redeploy of the container.
docker run --name proxy -p 8080:8080 -v {YOUR HOST DIRECTORY MOUNT PATH}:/application/work -d images.kgs-cloud.de/tia-proxy/tia-proxy:<version>Explanation:
Command | Task |
|---|---|
docker run | Start the container |
--name {APPLICATION NAME} | gives the container a freely selectable name while running (to have a simpler reference for later). Hint: You can start multiple instances of the same containers with different ports and different names. Example: --name MyProxy |
-p {PORT}:{PORT} | Maps the host port to the port in the container. Our Software runs on 8080 inside the container, therefore you always want to map your arbitrary host port to 8080 Sample: -p 8080:8080 |
-v {HOST_MOUNTDIR}:{CONTAINER_MOUNTDIR} | In order to put the configuration outside of the container, its necessary to mount the /application/work directory of the container into an arbitrary host directory Example: -v C:\KGS\cloud\mount:/application/work |
-d {IMAGE NAME} | The Image to run Requires Step 1 (pull) to be completed first Example: -d http://images.kgs-cloud.de/tia-proxy/tia-proxy:<version> |
HTTPS-Configuration with HTTPS
See Configuring tia® Classic and tia® Core for HTTPS (container deployment)