One of the alternatives for installing Curiosity is to run it as a Docker container. This is the easiest way to get started and keep your deployment up-to-date.

Prerequisites

Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. In order to get started, you will need to have a working Docker installation on your machine or server.

You can follow the official Docker documentation on how to install it on your operating system.

Docker Image

The Curiosity Docker Image is available in the official Docker repository.

You can download the image from the registry using docker pull:

docker pull curiosityai/curiosity

This will pull the latest available image from the Docker registry.

To hard-code your deployment to a specific version, you can add the version number on the end of the command - this is recommended for production instances where you would like to have more control over deploying updates.

docker pull curiosityai/curiosity:VERSION

Configuration

Configure Curiosity using environment variables when you start the container. See Configuration for a list of all configurable variables.

You must configure the values that are required for a standard installation. Unlike in the Installation guide, you cannot use a YAML file in the root folder of the app, therefore pass the configuration variables directly to the docker run command:

mkdir -p ~/curiosity/storage

docker run \
-p 8080:8080 \
-v ~/curiosity/storage/:/data/ \
-e MSK_GRAPH_STORAGE=/data/ \
curiosityai/curiosity

If you're running on Windows, you will need to adapt the directory like as required:

mkdir c:\curiosity\storage
docker run \
-p 8080:8080 \
-v c:/curiosity/storage/data/ \
-e MSK_GRAPH_STORAGE=/data/ \
curiosityai/curiosity

You should be able to navigate on your browser to the port mapped on the file:

http://localhost:8080.

The username and password for your first log is in both cases: admin.

It is recommended that you change the admin password immediately to a secure one.

Did this answer your question?