Additional parts of the environment in which your application is executed are specified below.
The following environment variables are injected in the container:
KBC_DATADIR: This is always
/data/in KBC; use this environment variable during application development to create development and testing environments.
KBC_RUNID: RunId from Storage; it couples all events within an API call (use this for logging)
KBC_PROJECTID: Id of the project in KBC.
KBC_CONFIGID: Id of the configuration or hash of configuration data if the configuration is not named (
configDatawas used in API call).
KBC_COMPONENTID: Id of the component
The following variables are available only if specifically requested in the component registration (and approved by us):
KBC_PROJECTNAME: Name of the project in KBC.
KBC_TOKENID: Id of the token running the container.
KBC_TOKENDESC: Description (user name or token name) of the token running the container.
KBC_TOKEN: The actual token running the container.
KBC_URL: The Storage API URL.
KBC_LOGGER_ADDR: IP address of GELF server
KBC_LOGGER_PORT: Port of the GELF server
The script defined in Dockerfile
ENTRYPOINT should provide an exit status. The
following rules apply:
exit code = 0The execution is considered successful.
exit code = 1The execution fails with a User Exception; the contents of both STDOUT and STDERR will be sent to Storage API Events.
exit code > 1The execution fails with an Application Exception and the contents of both STDOUT and STDERR will be sent to internal logs.
It is fairly important to distinguish between a User Exception and Application Exception. In case of User Exception, the end-user will see a full error message. Therefore,
In case of an Application Exception, the end-user will see only a canned response (‘An application error occurred’) with the option to contact support. The actual output of the application will be sent to our internal logs only. You can request us to retrieve the internal logs.
In case of Docker extensions the output can be forwarded to a place specified by you in your
component registration, while in case of Custom Science, it cannot.
It is possible to modify the above behavior so that regardless of the exit code, all errors are User Exceptions. This is done
no_application_errors during component registration.