# Containers tab

Source: https://www.storeframe.io/docs/hub/environments/containers

Per-service Docker container health, version management, and restart actions for a single environment.

Each StoreFrame environment runs the Magento stack as a set of Docker containers on the VM. The Containers tab shows the health of each service and lets you restart or update any that are misbehaving.

## What you'll see

Containers are displayed as cards in a grid. Each card shows:

* **Service name** the Docker service identifier
* **Status** Running, Restarting, Exited, and so on
* **Uptime** time since the container last started
* **Restart count** automatic restarts since last provision
* **CPU and memory** live resource usage figures streamed from the environment
* **Current image tag** the version currently running

![Containers tab showing a grid of service cards](https://www.storeframe.io/assets/docs/hub/containers-tab-showing-grid-of-service-cards.png)

## The stack

Every environment provisioned by StoreFrame ships the same containerized stack:

| Container             | Role                                                                                                    |
| --------------------- | ------------------------------------------------------------------------------------------------------- |
| **nginx** (OpenResty) | Web server, TLS termination, Lua security pipeline — rate limiting, proof-of-work, application firewall |
| **php** (FrankenPHP)  | Magento PHP runtime with worker mode and HTTP/3 support                                                 |
| **mariadb**           | Primary database, auto-tuned for Magento workloads                                                      |
| **redis**             | Session storage, full-page cache backend, and distributed locks                                         |
| **opensearch**        | Product and category search indexes                                                                     |
| **varnish**           | Full-page cache in front of nginx                                                                       |
| **rabbitmq**          | Message queue for Magento async consumer jobs                                                           |
| **nodejs**            | Hyvä theme asset build pipeline                                                                         |
| **crowdsec**          | Behavioral firewall and WAF                                                                             |
| **helio**             | StoreFrame metrics, container logs, and platform log agent                                              |

Each service has its own page under [/developer/stack](/docs/infrastructure/stack).

## Service actions

Each card's action menu lets you:

* **Install** (re)installs the service from your environment's settings. Use it to apply changes you made in the environment file (`.env`), or to add a service the environment doesn't have yet.
* **Restart** bounces the container. It does not re-read `.env`, so it won't apply configuration changes.
* **Stop** stops the container without removing it

Reinstalling **redis** clears all sessions and logs shoppers out, so do it outside busy hours.

Most containers are safe to restart at any time. Avoid restarting **mariadb** during peak traffic — it interrupts in-flight queries. If MariaDB needs a restart, do it during off-peak hours or when you are already handling an incident.

## Version management

Containers that have available image versions show a version selector on their card. Select a version from the dropdown and click **Apply** to pull the new image and restart the service. This is how you update individual stack components without a full re-provision.

For a service that isn't installed yet, only **Install** is shown. Use it to add a service to an environment that was provisioned before that service was introduced.

## Live updates

Container stats stream in real-time over a persistent WebSocket connection from the environment. The **Refresh** button forces a manual state resync if the live data looks stale. A connection indicator in the header shows whether the live stream is active.
