Deploy a Container Appliance

This tutorial walks you through the complete lifecycle of deploying a container appliance. By the end of this guide, you will have a fully functioning appliance hosting containers, and your end-users will be able to access them through their Reemo interface.

1. Initialize
dns

Create the container provider in appliance mode.

Step 1: Initialize the Container Provider
2. Create
architecture

Create the container blueprint.

Step 2: Create Container Blueprints
3. Associate
hub

Link the container provider to the Organization.

Step 3: Associate Blueprints to Organizations
4. Configure
box_edit

Create the container profile.

Step 4: Configure Container Profiles
5. Connect
rocket_launch

Open user access!

Step 5: Connect Users

Prerequisites

  • Administrator access to your Reemo instance.

  • An active organization already created on your instance.

Step 1: Initialize the Container Provider

To host your containers, you first need to declare a new provider in appliance mode in your portal, then deploy the local agent that will communicate with Reemo.

  1. Review the hardware, network, and sizing prerequisites in the Provision the Appliance guide.

  2. Choose your deployment mode and follow the corresponding installation steps:

Checkpoint: Ensure your appliance is visible and reporting as “Online” in your Instance dashboard before proceeding.

Step 2: Create Container Blueprints

Container blueprints define the technical configuration of your environments (image, resource limits, environment variables).

To set this up, you need to configure a new container blueprint in your Admin Area. Follow the step-by-step instructions in the Manage Container Blueprints guide to create your first blueprint (e.g., a secure Chromium browser or an SSH sandbox).

Step 3: Associate Blueprints to Organizations

Now that your infrastructure and blueprints are ready, you must grant an Organization the right to use them.

Navigate to your Container Providers settings to link the container blueprints you just created to the target Organization. See the Associate a Private Provider with an Organization guide for exact instructions.

Step 4: Configure Container Profiles

The Organization now has access to the container blueprints, but needs to define how users can consume them.

This is done by creating a Container Profile in the Organization management interface. Refer to the Containers guide to select your blueprint and define usage policies (such as duration and limits).

Step 5: Connect Users

The final step is to grant your end-users access to the newly created Container Profile.

Navigate to the Users section of your Organization. Refer to the Manage Users guide for detailed steps on assigning the target users or groups to the Container Profile.

Result: When the assigned users log in to Reemo, they will now see the option to launch the container environment directly from their dashboard.