Container Management

Containers allow users to run isolated environments (e.g., secure browsing sessions or specific applications). They are based on Container Profiles that define their configuration and operating rules.

Important

This feature is available starting from the Enterprise plan.

It is subject to the Reemo Containers licensing model.

Container Profiles

Container Profiles act as templates. They define the image, constraints, and options applied to the containers generated from them. When a user assigned to this profile logs in, their container automatically appears in their list.

List of Profiles

Overview of available container profiles.

The Container Profiles page lists all container profiles defined in the organization. Each table row displays the following information:

• Name: the name of the Container Profile.

• Container Provider: the infrastructure used to run the container (e.g. Reemo SWARM1).

• Image: the base image used (e.g. Chromium).

• Expire after: the time limit before the container automatically stops after disconnection.

• Managing Group: the group responsible for managing the profile, if defined.

• Created At: date and time when the profile was created.

This view allows quick verification of available profiles, their basic configuration, and governance status.

Create a New Profile

1. Navigate to your organization and open Container Profiles.

2. Click New Container Profile.

3. Select the source of your profile:

   • Instance Administrator : Select a Provider, an Image, and optionally a Container Blueprint (if defined).

   • Organization Administrator : Select a Container Blueprint (pre-configured environment template).

4. Configure the remaining settings, clicking Next after each step:

   • Settings: Define the container profile settings such as its name and the container expiration delay after disconnection.

   • Options: Configure the image deployment options. Note: These options depend on the selected image and are defined by the instance administrator who manages deployed images.

   • Clipboard restrictions: enable/disable read and write access

   • File transfer: Enable or disable file transfers.

   • Sessions: Set the idle timeout behavior to auto disconnect idle sessions.

   • Constraints: Define specific rules such as placement rules (e.g. location) for the profile.

   • Labels: Add labels to your containers to filter or identify them in your cluster. A label consists of a key and a value (e.g., environment=production).

5. Click Create to finalize the Container Profile.

Container profile creation screen.

Edit a Profile

You can edit an existing profile to adjust its parameters (name, expiration, constraints, advanced options).

Editing a container profile with options and constraints.

Assign Users to a Profile

Users must be associated with a Container Profile in order to launch containers.

1. Open the container profile.

2. Click Assign users.

3. Select the users and confirm.

User assignment window for a profile.

Profile View

Information of a container profile (name, image, expiration, provider, managing group).

A Container Profile displays the following details:

• Name: profile name.

• Image: the image used to run the container (e.g. Chromium).

• Container Provider: the infrastructure on which the containers will be deployed (e.g. Reemo SWARM1).

• Expire after: maximum container lifespan after disconnection.

• Managing Group: group responsible for the profile (if defined).

• Usage Schedule: usage schedule applied to the profile (default: None = unlimited).

• Created At: date and time of profile creation.

From this page, you can:

• Edit profile parameters (name, image, constraints, advanced options, etc.).

• Assign users to the profile.

• Delete the profile from the organization if needed.

An additional tab shows the users associated with this Container Profile.

Container profile with assigned user.

File Transfer

The File Transfer feature allows users to exchange files between their local machine and a container during an active session. It is configured at the container profile or organization level, and supports independent upload and download controls, file type restrictions, size limits, and log anonymization.

Access: Edit a container profile > File Transfer step.

Configuration Options

Each setting uses a dropdown with three states:

• Enabled: The setting is active for this profile.

• Enabled (Organization): The setting is active and inherits the configuration defined at the organization level.

• Disabled: The setting is turned off for this profile.

Some settings reveal additional sub-options when set to Enabled.

File transfer configuration in a container profile.

Note

Enabling File Transfer reveals the Upload and Download sections but does not activate them. Upload and Download must each be enabled individually to take effect.

Upload

• File Upload: Enables or disables file upload for users of this profile.

• File types Whitelist: Restrict uploads to specific file types. When set to Enabled, the organization-level list of authorized types applies automatically.

  • Override allowed file types (checkbox): When checked, replaces the organization-level list with a custom selection. Use the dropdown that appears to select the authorized file types for this profile.

• Limit Upload Size: Restrict uploads by file size. When set to Enabled:

  • Override Max Upload Size (1 MB) (checkbox): Override the organization-level size limit. When checked, specify the maximum file size per upload (in MB).

Download

• File Download: Enables or disables file download for users of this profile.

• File types Whitelist: Restrict downloads to specific file types. When set to Enabled, the organization-level list of authorized types applies automatically.

  • Override allowed file types (checkbox): When checked, replaces the organization-level list with a custom selection. Use the dropdown that appears to select the authorized file types for this profile.

• Limit Download Size: Restrict downloads by file size. When set to Enabled:

  • Override Max Download Size (1 MB) (checkbox): Override the organization-level size limit. When checked, specify the maximum file size per download (in MB).

Log Anonymization

• Anonymize file transfer logs: In service logs, omits filenames and replaces the session user with their SHA256 hash. Also applies outside file-transfer events wherever the username appears (e.g., connection notifications).

User Workflow

Once enabled in the container profile, file transfer is accessible via the Reemo toolbar during an active session. Files are exchanged through the /home/reemo/Downloads directory inside the container.

Files in the /home/reemo/Downloads directory appear automatically in the File Transfer menu of the Reemo toolbar as available downloads. Conversely, when you upload a file via the toolbar, it is automatically saved to the same directory.

Warning

The /home/reemo/Downloads directory is ephemeral: its contents are permanently lost when the container stops. Users must download any files they need to their local machine before ending their session.

Note

Transfers are subject to the restrictions configured in the container profile (allowed file types, size limits). A transfer that exceeds the configured limit or uses a non-allowed file type will be rejected.

File transfer menu in the Reemo toolbar.

To upload a file (local machine → container):

1. During an active container session, open the File Transfer menu in the Reemo toolbar.

2. Select the file(s) to upload from your local machine.

3. The uploaded files appear in the /home/reemo/Downloads directory inside the container.

To download a file (container → local machine):

1. In the container, move or save the file(s) you want to retrieve to /home/reemo/Downloads.

2. Open the File Transfer menu in the Reemo toolbar.

3. The files stored in /home/reemo/Downloads appear in the menu. Select the file(s) to download. They are saved to your local machine’s default download folder.

To delete a file:

1. Open the File Transfer menu in the Reemo toolbar.

2. Click the delete button () next to the file.

3. Confirm the deletion in the dialog that appears.

Delete confirmation dialog.

Containers

Once Container Profiles are configured and assigned, users can launch containers. Each container represents a running instance visible in the Containers section.

List of Containers

Overview of active or stopped containers.

The columns display:

• Name and Hostname

• OS and version

• IP

• Status (Online, Offline, Busy)

• Used Profile

• Associated Collection (if applicable)

• Owning User

• Creation Date

Container Profile View

Container information (OS, status, user, associated profile, activity logs).

Container Collections

Assign Container Profiles to a Collection

A Collection does not directly contain containers but rather Container Profiles. By assigning one or more profiles to a Collection, you define which environments will be available to users associated with that Collection.

1. Open the desired Collection profile.

2. Click on the Container Profiles tab.

3. Press the Assign container profiles button.

Selection window for adding Container Profiles to the Collection.

4. Select one or more container profiles from the list.

5. Click Assign to confirm.

The selected Container Profiles now appear in the Collection’s Container Profiles tab, displaying their key details (name, image, provider, expiration date, etc.).

Container Profiles successfully assigned to a Collection.

• A user must be assigned to a Collection to access the Container Profiles it contains.

• Access rights and options remain those defined in the original Container Profile.

• You can add or remove Container Profiles from a Collection at any time.

Summary

Container management is based on two main concepts:

• Container Profiles: A container profile defines a container’s configuration (image, constraints, options, restrictions). It can be assigned directly to users to provide them with specific environments.

• Collections: A collection groups one or more container profiles and assigns them to a set of users. This simplifies centralized management of standardized environments (e.g., “Internet Navigation”, “DevOps”, etc.).

In summary:

• Use container profiles if you want to create and assign environments individually (one profile = one configuration).

• Use collections if you want to manage sets of environments and distribute them easily to multiple users.