Containers
Manage Docker containers and cloud workloads
BeyondTrust Gateways
The dashboard always keeps one gateway per cloud for its own tunnels and jumps, and removes it once nothing is using it. Add your own to carry session traffic — as many as you want, in whatever regions you want. They join the same PRA Gateway as additional cluster nodes, so nothing needs repointing.
Only regions with a per-region config set are listed — add one under Settings → Multi-region to deploy elsewhere. A region without its own subnet would put the gateway on the default region's network. Blank zone uses .
| Status | Name | Cloud | Region | Host | Created by | Actions |
|---|---|---|---|---|---|---|
| Loading… | ||||||
| No gateways yet. The managed one appears here the first time the dashboard needs it. | ||||||
| managed | Job | |||||
A gateway in error kept its row so the reason stays visible — open its job for the detail. Hover any status for the reason behind it.
missing means the host is no longer in the cloud and nothing asked for it to be removed. Remove the row, or deploy a replacement to take over its share of the session load.
degraded means the host is up but is not running the gateway task, so it cannot broker a session — the Cloud tab's ECS Tasks list shows the same thing. The next deploy that needs this gateway starts the task.
Portainer is not configured
Manage Docker hosts — cloud or on-prem — from this page by either deploying a managed Portainer CE server above, or connecting one you already run — set its URL and API token in Settings → Integrations → Portainer CE.
Portainer connection error
Check the Portainer URL, API token, and SSL settings in Settings → Integrations → Portainer CE.
Containers
Fetching containers from Portainer…
| Name | Image | Status | Ports | Actions |
|---|---|---|---|---|
| — |
|
Stacks
| Stack Name | Status | Type |
|---|---|---|
ECS Tasks
ECS error
| Task ID | Definition | Containers | Status | Started | Stopped | Actions |
|---|---|---|---|---|---|---|
Azure Container Instances (ACI)
| Name | State | CPU / Memory | Containers | Created | Actions |
|---|---|---|---|---|---|
| Running Failed |
|
GCE Container Instances
| Name | Purpose | Zone | Machine | Container Image | Status | Actions |
|---|---|---|---|---|---|---|
Both run as containers on Container-Optimised OS GCE instances. Gateways are recreated automatically on the next VM deploy; Compose instances are deployed via + Deploy Compose. Stop / Delete removes the COS instance.
GCP Cloud Run Jobs
| Name | Purpose | Region | Image | Status | Created |
|---|---|---|---|---|---|
Ansible, image-promote, and Kubernetes runners execute as ephemeral Cloud Run Jobs and are removed when they finish — only the ones still in flight are listed here.