Container Blueprints

The Container Blueprints feature acts as an intermediary template between the technical infrastructure and the end-user access. Instance Administrators create blueprints to simplify setup for Organization or Group Administrators.

A container blueprint allows you to:

  • Pre-select the Provider and Image so they cannot be changed later.

  • Lock specific fields, such as clipboard access or configuration, to enforce security policies.

  • Hide technical details from Organization or Group Administrators.

Note

Blueprints are templates. You cannot launch a container directly from a blueprint. An Organization or Group Administrator must first use it to create a Container Profile.

Creating a Container Blueprint

  1. From the Admin Area, navigate to Container Blueprints, and then click New Container Blueprint. Tip: You can also create a container blueprint directly from an image. Go to Images , select an image, navigate to **Container Blueprints*, and then click Create Container Blueprint.*

  2. Select your Container Provider and Image (if you didn’t start from an existing image). Note: Once the blueprint is created, the Image and Container Provider cannot be modified.

  3. Configure the default settings for the container.

  4. Optionally, Lock the specific parameters you want to enforce (e.g., disable file transfers or lock login credentials).

    Note

    For Organization or Group Administrators, locked configuration settings are hidden, while locked security settings (like file transfers) remain visible but read-only.

  5. (Optional) Assign Applications to the blueprint. These are automatically included when a profile is created from this blueprint. You can Lock them to prevent Organization or Group Administrators from removing them. Note: this option is available for “Iron” containers only.

  6. If necessary, create Constraints to restrict which servers (workers) are allowed to host these containers (e.g., restricting a heavy application to servers with GPUs).

  7. Click Create to save the blueprint.

Assigning a Blueprint to an Organization

If the association between the Container Provider and the Image used by your blueprint is private, you must assign the blueprint to an organization before it can be used. If this Provider-Image association is public, the blueprint is automatically available, and you can skip this section.

Step 1: Verify Provider Access

  1. From the Admin Area, navigate to Organizations and select the target organization.

  2. Go to Container Provider.

  3. Verify that the provider associated with your blueprint is listed. If it is not, assign it to the organization before proceeding.

Step 2: Assign the Blueprint

  1. Still within the selected organization, navigate to Images.

  2. Click Add Private Image.

  3. In the dialog box, select the matching Provider and Image.

  4. Select your specific Blueprint from the dropdown menu. Note: A blueprint only appears here if it is associated with the Provider and Image you selected in the previous step.

  5. Click Save.

The blueprint appears in the organization’s list of available images. Organization Administrators can now select this blueprint when creating a new Container Profile (see Creating a Container Profile).