FAQ

Docker commands fail or default credentials don't work for me

It has been tested that the Docker installation fails with versions like 1.29.2. Upgrade your docker-compose version to a recent one because the Rekono docker-compose.yml uses modern syntax that needs it.

Permission error during Nginx execution

The reason for the following Nginx failure is the lack of permissions from Docker execution over docker/nginx/tls/ directory:

nginx | req: Can't open "/etc/nginx/tls/privatekey.key" for writing, Permission denied

It could happen when the Rekono repository is cloned using one system user and Docker is being executed with another system user. To solve the problem, it's needed to give read and write permissions over the directory docker/nginx/tls/ to the system user that is executing Docker. For example, the following command can be used to give read and write access to all system users:

chmod -R 666 docker/nginx/tls/

How can I change the port where Rekono is running?

In Docker environments, the Rekono ports can be easily changed in the docker-compose.yml file:

nginx:
    restart: always
    build:
      context: .
      dockerfile: docker/nginx/Dockerfile
    image: rekono-nginx:latest
    hostname: nginx
    container_name: nginx
    ports:
      - <custom http port>:80
      - <custom https port>:443

This way, exposed Nginx ports are mapped to specific custom local ports.

How can I deploy Rekono under a specific web path?

The web path where Rekono is deployed should be managed using a reverse proxy like Nginx. In Docker environments the nginx.conf file can be customized for that.

Moreover, the frontend must be configured to use the correct backend endpoints. For that, the .env file in the frontend root directory (see Configuration) should be configured:

VUE_APP_ROOT_BACKEND_PATH=/<my web root path>

Finally, it's needed to configure the backend with the environment variable RKN_ROOT_PATH or the rootpath property (see Configuration), to apply the custom web path in the API REST documentation.