...
| Placeholder name to be replaced | Mapping to container-configuration | Explanation | ||
---|---|---|---|---|---|
| <Name> | Give the tia Core container a custom name. This name is also the application context name.
| |||
| <Hostport> |
| <Hostport>: Listener port on host that forwards to the listener port in the container, which is configured by | ||
| <Config Folder> |
| The folder location on host system where the | ||
| <License Folder> |
| The location on host system where the license file resides. For more information refer to Location of the license file . | ||
| <Temp Folder> |
| Optional: Mapping container’s | ||
| <Loglevel> |
| The log level sets the verboseness of the log writing. Valid are: | ||
| <BcryptHash> |
| To login to the tia Status UI, a password is required that when being hashed must match this value. For more information refer to tia® Status UI Authentication . | ||
| Run as daemon in background | ||||
<Image> | Referencing the image as last parameter in the The image is referenced like this:
with <Product>: The tia Core product to be deployed: <Version>: The version of tia Core to be deployed. kgs recommends to use the latest available version. For this use |
Template of docker run
command for copy & paste:
Code Block |
---|
docker run --name <Name> -p <Hostport>:<Containerport> -v data_volume:/temp/data -v <License Folder>:/application/config/license/ -v <Config Folder>/repository.cfg:/application/config/repository.cfg -e LOGGING_LEVEL_ROOT=<Loglevel> -e WEBAPP_SECURITY_AUTH_BASIC_PASSWORD="<BcryptHash>" -d <Image> |
Example:
Code Block |
---|
docker run --name tiacore-AL -p 8080:8080 -v data_volume:/temp/data -v ./tiacore/license:/application/config/license/ -v ./tiacore/repository.cfg:/application/config/repository.cfg -e LOGGING_LEVEL_ROOT=INFO -e WEBAPP_SECURITY_AUTH_BASIC_PASSWORD="\$2a\$10\$5E1KpGIKSq6xuWmGf92bheB17V0l4fEMnVmYPqhWiazKddcx1TF/e" -d images.docker.kgs-cloud.de/tia/core/saphttp:latest |
Explanation of docker command:
The parameter -p
maps ports, and -v
volumes (directories or files) between host and container. -e
sets environmental variables in the container.
Using -v
allows to store data like configuration permanently at host, edit, maintain it there, even when the container is started, destroyed and restarted again.
Info |
---|
Hint: When host is running Windows, the path may contain drive letter with colon ( E.g.: |
For information about the environmental variables set, refer to Reference of application-wide parameters .For information about the container environmental variables, refer to Reference of application-wide parameters
For example deployments see: