Skip to content

FAQ

Jump to bottom
Pablo Santiago edited this page Mar 7, 2023 · 3 revisions

Docker commands fail or deafult 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 use modern syntax that needs it.

How can I change the port where Rekono is running on?

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

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

How can I deploy Rekono under 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.

Installation via Rekono CLI is not working properly, what can I do?

⚠️ Installation and services management features will be removed from rekono-cli in the next release. This installation method has been deprecated because it's difficult to mantain, it's unstable because sometimes some errors occur in some machines and it deploys a debug version of Rekono frontend that is a bad and insecure practice. Rekono will offer new installation method for local environments soon. By the time, check installation alternatives.

However, if you want to continue with the CLI installation, you can try the following:

  • Execute the failed steps manually in your machine, and retry the installation process

  • Change local user used to execute the installation command. Usage of root or no-root users have implications in the installation paths of dependencies

Clone this wiki locally