Single Machine Installation

The easiest way to start using Hopsworks locally is to import a VirtualBox appliance (ova) or let the Karamel installation software install Hopsworks in a vm by running the script.

Both ways are described in detail below.

Importing an ova image

To successfully import and start the image, it is necessary to have VirtualBox installed on your workstation and at least 20GB of storage and 16GB of memory available. You can then follow these steps to import Hopsworks:

  1. Download the image.
  2. Import the image from the VirtualBox GUI or from the command line with vboxmanage import hopsworks-0.10.0.ova
  3. Start the vm in headless mode from the VirtualBox GUI or from the command line with vboxmanage startvm hopsworks0 --type headless
  4. Wait for approximately 3 minutes until all services have started and then access Hopsworks at https://localhost:64724/hopsworks/ and login with username: and password: admin. For further details on how to use Hopsworks, see User Guide.

Advanced users might want to ssh in the vm. To do this, you need to:

  1. Download the ssh key.
  2. Then do ssh -p 31989 -i insecure_private_key vagrant@localhost
  3. To view the status of all services, you can do sudo /srv/hops/kagent/kagent/bin/
  4. To find a particular forwarded port, you can do `` vboxmanage showvminfo hopsworks0 | grep <port>``

Deploying a Hopsworks vm with Karamel

If you are using a debian based distribution, you can run the script. (Tested on Ubuntu 18.04 LTS)


It is required that vagrant, virtualbox and chefdk are already installed on the host machine. If you run

./ --install-deps

the script will automatically download and install the required versions of these dependencies.

After installing the dependencies, it will create and deploy the VM (needs ~16GB of RAM). This operation might take up to 1 hour, depending on your host machine specs.

To trace execution progress, tail the nohup file.

tail -f karamel-chef/nohup

The script will ouput the port on which you can access Hopsworks when installation is completed and the demo user credentials.

If you want to destroy your VM, run the kill script


Going further

For detailed instructions on how to perform production deployments in-house or in the cloud, see Installation.