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¶
Access: inventory_2 Inventory > box_edit Container 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 profile’s name.
Container Provider: the infrastructure used to run the container (e.g. Reemo SWARM1).
Image: the base image used (e.g. Chromium).
Container Blueprint: the container blueprint used as a base for this profile, if defined.
Expire after: the time limit before the container automatically stops after disconnection.
Managing Group: the group responsible for managing the profile, if defined.
Create a New Profile¶
Navigate to your organization and open box_edit Container Profiles.
Click New Container Profile.
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).
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 (see File Transfer for the full list of options).
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 (see Container Placement Constraints).
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).
Warning
Do not confuse these Labels, attached to the container to filter or identify it, with the node labels used by placement Constraints (see Container Placement Constraints): the latter are attached to cluster nodes, not to containers.
Click Create to finalize the Container Profile.
Container profile creation screen.¶
Assign Users to a Profile¶
Users must be associated with a container profile in order to launch containers.
Open the container profile.
Click Assign users.
Select the users and confirm.
User assignment window for a profile.¶
Profile View¶
Container profile record.¶
A container profile record displays the following information:
Name: the profile’s name.
Container Provider: the infrastructure on which the containers of this profile will be created (e.g. Reemo SWARM1).
Image: the image used to run the container (e.g. Chromium).
Container Blueprint: the container blueprint used as a base for this profile, if defined.
Managing Group: group responsible for the profile (if defined).
Usage Schedule: usage schedule applied to the profile (default: None = unlimited).
Expire after: maximum container lifespan after disconnection.
Created At: date and time of profile creation.
Running Containers Limit: maximum number of containers that can run simultaneously for this profile (default: None = unlimited).
Two actions are available at the top of the record:
Duplicate: creates a new profile pre-filled with this profile’s configuration.
Edit: opens the edit form (same fields as Create a New Profile).
Available Tabs¶
Users: users assigned to this profile — see Assign Users to a Profile above.
Containers: active containers from this profile — see Containers.
Security Logs: history of actions related to this profile — see Security Logs.
Rights Review: tree of access rights linked to this profile — see Rights Review.
Credentials: secrets assigned to this profile — see Manage Credentials.
Delete Container Profile: permanently deletes the profile.
See also
Collections — Group several container profiles into a Collection to distribute them to a set of users.