Container Types and Use Cases

The platform combines system containers and application containers in one environment. Each technology is designed for different workload patterns, while the platform orchestration layer brings the benefits of both approaches together.

On this page

Container Types
Certified Managed Containers
Virtual Private Servers
Custom Docker Containers
Docker Engine CE
Kubernetes Cluster
Choosing the Right Option
What’s next?

Container Types

System Containers Stateful, operating-system-oriented containers that can run several processes. They resemble virtual machines and are suitable for traditional, monolithic, and legacy applications.

Application Containers Usually stateless, microservice-oriented containers that run a primary process and can scale horizontally. They are suited to immutable and short-lived infrastructures.

System-container implementations include LXC/LXD, OpenVZ/Virtuozzo, BSD Jails, and Linux-VServer. The platform uses Virtuozzo system containers. Application-container technologies include Docker, containerd, and CRI-O, with Docker used as the primary application-container technology.

Application container and system container comparison — System containers and application containers address different workload models.

Many cloud platforms run Docker application containers inside virtual machines. Each virtual machine adds a guest operating system with its own memory, CPU, and disk overhead. In this platform, Docker can run inside a system container while sharing the host kernel, reducing resource consumption while maintaining isolation.

System container compared with virtual machine — System containers use fewer resources than full virtual machines.

Certified Managed Containers

Certified managed containers are the most common and recommended option. The platform provides preconfigured and managed software stacks for application servers, load balancers, databases, build nodes, and other services.

Java, PHP, Node.js, Ruby, Python, and Go application servers
SQL and NoSQL databases
Load balancers and caching services
Storage and build nodes
Flexible multi-layer application topologies

The platform team tests and optimises certified stacks and regularly releases stable versions or security updates. These containers can also provide platform-specific integrations.

Resource-aware automatic configuration
Built-in vertical and horizontal scaling
Automated SSL certificate installation
Application deployment automation
Built-in auto-clustering
Managed delivery of security updates

Managed containers scheme — Managed containers are integrated with platform automation and lifecycle services.

Virtual Private Servers (Elastic VPS)

Elastic VPS is a straightforward system-container use case. It provides an operating-system-based container with distributions such as CentOS, Ubuntu, or Debian and without preinstalled application software.

This option is useful for legacy applications because migration from a virtual machine may require few or no architectural changes. The user is responsible for installing and configuring the required software, and root access is provided.

Elastic VPS behaves similarly to a virtual machine but uses fewer resources and can still benefit from automatic vertical and horizontal scaling.

Custom Docker Containers

A custom Docker container uses a compatible Docker image deployed inside a system-container runtime. The Docker image filesystem is unpacked into the platform container, making it compatible with many platform capabilities, including vertical and horizontal scaling.

Custom container scheme — A Docker image is deployed within the platform’s system-container runtime.

This option gives access to a broad range of third-party software images from Docker Hub and other compatible public or private registries. However, compatibility and reliable operation depend on the third-party image maintainer.

Custom Docker containers — Custom Docker images expand the available software-stack choices.

Important: Unlike certified containers, third-party Docker images are not fully managed by the platform team. Review the image architecture, operating-system requirements, updates, and security maintenance before using it in production.

Docker Engine CE (Docker Native)

The platform supports Docker Engine Community Edition running inside a system container while retaining compatibility with the native Docker ecosystem.

Docker Engine CE scheme — Docker Engine CE runs inside a system container.

This integration supports the primary Docker tools:

Docker Engine — builds from Dockerfiles or runs prebuilt images.
Docker Registry — stores and distributes public or private images.
Docker Compose — defines and runs multi-container applications through one compose file.

Kubernetes Cluster

Kubernetes is suitable for orchestrating complex containerised applications that require automated deployment, scaling, networking, service discovery, and lifecycle management across multiple nodes.

The platform can deploy a preconfigured Kubernetes cluster and provide tools for cluster access, upgrades, storage, backups, ingress management, and application deployment.

Choosing the Right Option

Certified Managed ContainerBest for standard application stacks, managed updates, automation, and rapid production deployment.

Elastic VPSBest for legacy, monolithic, or OS-level applications that require root access and custom configuration.

Custom Docker ContainerBest when a specific third-party or internally maintained Docker image is required.

Docker Engine CEBest for users who need direct Docker Engine, Registry, and Compose workflows.

Kubernetes ClusterBest for larger cloud-native systems composed of many independently managed services.