Home - Getting Started


HakunaCloud is a managed platform for developers and sysadmins to develop, deploy, and run applications with containers. The use of Linux containers to deploy applications is called containerization, and the underlying technology is mostly known as Docker;

With Docker, you can start a container on your local machine as host. With HakunaCloud you can to start a container on a remote, cloud-based server.

Deploy your first container in 3 minutes

To get started with HakunaCloud, be sure you meet the following prerequisites:

  • Register for an account;
  • Have NodeJS installed on your machine;

Yep, that’s it 😎.

1. Install the CLI

HakunaCloud is managed entirely with a Command Line Tool.

npm install -g @hakuna.cloud/cli

2. Login

The first step is to log-in or signup as new user.

hakuna user login

You can always verify if your are currently logged in, and the informations of your users, with the command

hakuna user info

3. Run a test container - nginx Web Server

hakuna volume create http_data --size 5
hakuna run --name some-nginx -p 80:80 -v http_data:/usr/share/nginx/html nginx

The break down of the above commands:

  • hakuna volume create creates a persistent volume of 5 GB, that will securely store the data for your container;
  • hakuna run creates and start a container:
    • --name: the name is mandatory and identifies your containers;
    • -p 80:80: expose the container to the internet;
    • -v http_data:/usr/share/nginx/html: mount the volume in the container

4. Where is my container?

hakuna ps

The output should be similar to this:

name        image  status   publish
----------  -----  -------  ----------------------------------------------------------------------------------
some-nginx  nginx  running  some-nginx.<region>.<account>.v1.hakuna.cloud:80 -> 80

ps gives a quick overview of the status of your containers. The status can be running, stopped or other intermediate states.

The publish attributes list all the FQDN and ports exposed by the container to the internet. The FQDN name is always made of these parts:

  • the <name> of the container;
  • the <region> where the container is running;
  • the <account> id that is the owner of the container;

You can see that nginx is running by browsing that url

Next Steps


Read the technical details of Volumes and Networks: