Identity & runtime

Docker

Name: Nexoxa Bridge
Author: Nexoxa

Containers, resource usage, and quick actions.

The story

These pages use illustrative scenarios to walk through real workbench panels. Sidebar labels, Bridge paths, and connection schemes match the app; characters and timelines are examples for learning.

Container restart loop eats CPU — Docker panel shows status, restart, resource charts.

Fix without memorizing docker compose flags.

Bridge path: /server/docker

Step 1

Container list

api-worker Restarting — logs hint OOM. Bump memory limit.
Stabilized.

Containers, resource usage, and quick actions. /server/docker.

Step 2

Quick actions

Restart from UI during incident — faster than compose on phone hotspot.
Works.

Restart/stop where permitted.

Step 3

Resource usage

Container memory chart explains host RAM spike.
Scale decision.

Pair Resources panel.

This panel appears in the Nexoxa Bridge left sidebar after you connect with the matching connection URL. See the connection docs above for postgresql://, ssh://, sftp://, s3://, or smtp:// examples.

Related connections

SSH connection URL