Skip to content

Latest commit

 

History

History
40 lines (26 loc) · 1.84 KB

docker.md

File metadata and controls

40 lines (26 loc) · 1.84 KB
Raw

KUKSA CAN Provider and Docker

It is possible to build can-provider as a Docker container

docker build -f Dockerfile --progress=plain --build-arg TARGETPLATFORM=linux/amd64 -t can-provider:latest .

The same container can be used for both connecting to Databroker and Server:

docker run  --net=host -e LOG_LEVEL=INFO can-provider:latest --server-type kuksa_databroker

docker run  --net=host -e LOG_LEVEL=INFO can-provider:latest --server-type kuksa_val_server

Pre-built Docker container

A pre-built Docker container is available in the repository.

KUKSA.val Server/Databroker Authentication when using Docker

The docker container contains default certificates for KUKSA.val server, and if the configuration file does not specify token file the default token file provided by kuksa-client will be used.

No default token is included for KUKSA Databroker. Instead the user must specify the token file in the config file. The token must also be available for the running docker container, for example by mounting the directory container when starting the container. Below is an example based on that the token file provide-all.token is used and that kuksa.val is cloned to /home/user/kuksa.val. Then the token can be accessed by mounting the jwtfolder using the -v and specify token=/jwt/provide-all.token in the default configuration file.

docker run  --net=host -e LOG_LEVEL=INFO -v /home/user/kuksa.val/jwt:/jwt can-provider:latest

Note that authentication in KUKSA Databroker by default is deactivated, and then no token needs to be given!