Custom Containers Deployment

The platform can create custom containers from standard Docker images stored in Docker Hub or another public or private registry. Custom containers retain the original image software while gaining platform capabilities such as scaling, monitoring, logs, alerts and file management.

Third-party image responsibility

The platform manages container deployment and infrastructure features, but the application inside a third-party image remains the responsibility of the image maintainer.

In this article

Deploy from Docker Hub
Configure the custom-container topology
Open and manage the container
Deploy from a private registry
Update repository credentials
Expected result

Deploy a Custom Container from Docker Hub

Open the topology wizard

Click New Environment in the upper-left corner of the dashboard.

Custom container topology wizard — Open the environment topology and switch to the Custom tab.

Select a topology layer

Switch to the Custom tab, choose the required layer and click Select Image. Separate layer blocks help organize application servers, databases, load balancers and additional services.

Quick StartShows popular or recommended images for the selected layer when enabled by the provider.

SearchFinds public images in Docker Hub.

CustomAdds images from custom or private registries.

FavoriteStores frequently used images for quicker access.

Select container image — Search, select or add a custom container image.

Search for the image

Open the Search tab, enter the full or partial image name and press Enter. Select the required result and choose the appropriate image tag.

✓

Image details and favorites

Use More details to open the repository page. Select the star icon to save an image in Favorites.

Docker image details and tags — Review repository details and choose the required image tag.

One image per layer

Different Docker images cannot be placed in the same layer. Add another standard or Extra layer when the environment requires an additional image.

Configure the Custom-Container Topology

Build the environment structure

Add all required images to separate layers and click Next.

Build custom container topology — Organize custom images across the required environment layers.

Configure resources and settings

Adjust cloudlets, disk limits, scaling, region, environment variables, links, volumes, ports and runtime settings in the same way as other platform nodes.

Create the environment

Enter the environment name and click Create. The new custom-container environment appears on the dashboard after provisioning completes.

Create custom container environment — Review the topology and create the custom-container environment.

Open and Manage the Container

Use the Open in Browser action beside a container, or open the environment domain. When the whole environment is opened, the application-server or load-balancer layer is used as the entry point.

Open custom container in browser — Open the deployed custom container from the dashboard.

502 error does not always indicate a damaged image

Some images do not start a web interface automatically. A 502 response can also occur when the container has no public IP and the application is not listening on backend port 80. Verify running processes through SSH and confirm the HTTP service and port configuration.

Further configuration can be completed through the built-in File Manager or Web SSH. These tools provide root-level access for container administration.

Deploy from a Custom or Private Registry

Images from a custom registry can be saved in the Custom section and managed in the same way as public images. Credentials are stored so that later scaling and redeployment operations can authenticate automatically.

Add a new image

Open the Custom tab in the image selector and click Add New Image.

Add image from custom registry — Add a new image from a custom or private registry.

Enter repository information

Enter the repository name. The registry host can be omitted for Docker Hub images.

Add private-registry credentials

For a protected repository, enter the username and password. Leave these fields empty for public repositories, then click Add.

✓

Image tags

A tag does not need to be specified when adding the image. Choose the required tag during container creation. Available tags are refreshed automatically.

Private registry credentials — Enter repository details and credentials when required.

The image is added to the Custom list. It can be selected for deployment, marked as a favorite or removed using the bin icon.

Update Repository Credentials

Open additional container actions

Hover over the required layer, expand Additionally and select Repo Credentials.

Enter the updated login details

Provide the new repository login and password.

Apply the changes

Click Apply so future scaling and redeployment operations use the updated credentials.

Update container repository credentials — Update repository credentials for an existing custom container.

Expected Result

The selected public or private image is deployed as a managed custom container. It can be scaled, monitored, configured and redeployed through the platform while preserving the software supplied by the original image.

Important Notes

Use images that meet the platform’s supported operating-system and architecture requirements.
Choose separate layers when the environment requires different Docker images.
Verify image documentation, exposed ports and required variables before deployment.
A browser error may indicate that the image does not expose a web service rather than a failed deployment.
Store valid private-registry credentials so scaling and redeployment can authenticate successfully.
Prefer certified platform containers when regular testing, maintenance and guaranteed template compatibility are required.