A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another. Containers are not virtual machines - they provide isolation at a process-level.
HakunaCloud is a container engine that allows you to run containers without having to manage servers or clusters. This removes the need to choose server types, decide when to scale your clusters, or optimize cluster packing.
With HakunaCloud, all you have to do is packaging your application in containers and specifying the CPU and memory requirements for it.
HakunaCloud containers are 100% compatible with Docker containers, allowing you tu run your container in all your development stack - from your local dev machine up to the production environment - using the same api interface.
Running a container in the cloud is as simple as:
beekube run --name hello-world nginx
HakunaCloud supports the following options:
--cpus <number>: Number of CPUs
-e: Set environment variables
--name: required the name of the container
--network <value>: Connect a container to a [Networks]/docs/networks.html
-p: Publish a container port on the internet. A public IPv4 is attached to the container, and the
<public_port>is accessible to the internet
--volume <volume_name>:<container_path>: Mount a [Volume]/docs/volumes.html
The container is assigned 2 GB of
memory for each
cpu assigned. The container is billed if is in the state
## Stop a container
beekube stop <name>
beekube start <name>
beekube rm <name>
beekube hakuna <name> --hostname <hostname>
If you want to cofnigure a container as a VHost in Hakuna Cloud, you can just run previous command. You have to provide an hostname and configure DNS to point the hostname to one of our public load balancers.
Europe: eu1.lb.hakuna.cloud North America: na1.lb.hakuna.cloud
If you want a FQDN as test hostname, you can generate it using the Hakuna CLI runnign the following command and follow the instructions.
hakuna hostname create