Configuration file
The KESL container configuration file uses the yaml format. To read the settings from the file, mount the /root/kesl-service/config/ path on the device where the KESL container is installed, and specify the name of the configuration file if it differs from the default one. Thus, you can specify individual configuration file for each set of KESL containers.
Example: starting a KESL container
|
The table below shows the configuration file settings and the corresponding environment variables.
Correspondence between the settings and the environment variables
Configuration file setting |
Environment variable |
|---|---|
Common section |
|
port: <port for listening> |
# KRAS4D_PORT=8085 |
sqlpath: <full path to the database file that contains scan results> |
# KRAS4D_SQLPATH |
certdir: <path to the directory with registry certificates> |
# KRAS4D_CERTDIR |
keypath: <path to the directory with license keys> |
# KRAS4D_KEYPATH |
tmppath: <full path to the temporary directory> |
# KRAS4D_TMPPATH |
logpath: <full path to the event log> |
# KRAS4D_LOGPATH |
loglevel: [noset|debug|info|warning|error|critical] |
# KRAS4D_LOGLEVEL |
Control section |
|
xapikey: <request authorization key> |
# KRAS4D_XAPIKEY=None |
forceupdate: <forced database update at container start [True|False]> |
# KRAS4D_FORCEUPDATE |
activation: <activation code or key file name from /root/kesl-service/config/> |
# KRAS4D_ACTIVATION |
detectaction: [delete|skip] |
# KRAS4D_DETECTACTION |
scanoptions: <scan settings [ScanArchived=yes ScanSfxArchived=yes ...]> |
# KRAS4D_SCANOPTIONS |
skipimageifexist: <do not scan the image if it already exists on the server to which the scanned image is to be copied> |
# KRAS4D_SKIPIMAGEIFEXIST |
generaltimeout: <maximum time to wait for application commands to run> |
# KRAS4D_GENERALTIMEOUT |
updtasktimeout: <maximum time to wait for application database update tasks to run> |
# KRAS4D_UPDTASKTIMEOUT |
Repositories section |
|
<server>:<port>: address and port of the image registry that requires authorization when requesting for verification. |
|
Credentials subsection |
|
user: user name for authorization in the image registry |
|
pass: password for authorization in the image registry |
|
Example of a configuration file
|
