Containers

Git Web Manager

Docker, Kubernetes, and database workflows from a single workspace.

Overview

The Containers workspace provides controls for both /docker and /kubernetes.

The docker tab registers /docker for docker-specific controls, with some enterprise only functions.

The enterprise only /kubernetes package registers Kubernetes-specific controls. When the enterprise package is not installed, the page shows an infrastructure overview and upgrade prompts instead of live controls.

Community vs Enterprise

  • Community Edition includes Docker workflows with up to 3 nodes.
  • Enterprise Edition unlocks unlimited nodes and advanced infrastructure automation.
  • Automatic project and container audits are Enterprise-only.
  • White Label configuration is Enterprise-only.

Container Sections

  • Overview/Resources for workspace health and summaries.
  • Nodes for Docker host registration and lifecycle management.
  • Containers for runtime controls, status, and logs.
  • Deployments for Docker and Kubernetes deployment history.
  • Builds for build jobs and pipeline output.
  • Databases for managed containerized services (for example PostgreSQL/MySQL).
  • Kubernetes controls are grouped inside the Containers workspace rather than a separate top navigation item.

Grouped Views

  • The Containers section groups rows into collapsible Managed and External sets.
  • The Images section groups images by related container usage for quicker cleanup workflows.
  • The Volumes section groups volumes by container context, with an unassigned group for unmatched volumes.
  • Inspect output now opens in a structured modal with readable key/value cards plus raw JSON.

Build from Project (Images)

The Images section includes a Build from Project button (Enterprise) that lets you pull images from a project's Docker Compose file without leaving the UI.

  • The button is visible when at least one project has a detected docker-compose.yml or compatible compose file.
  • Clicking the button opens a modal listing each compatible project and the services defined in its compose file, along with the resolved image reference for each service.
  • Services whose image is already present locally show a Pulled badge (green checkmark) so you can avoid redundant pulls.
  • Click Pull (or Re-pull for already-pulled images) to queue a docker pull for that image. The pull runs through the standard pull workflow and output is shown in the pull log panel.

Services defined with a build context rather than a pre-built image reference are skipped in the modal — only services with a resolvable image: field are listed.

Configuration

Set container binary overrides in .env when needed:

  • GWM_DOCKER_BINARY (default: docker)
  • GWM_KUBECTL_BINARY (default: kubectl)

Notes

  • Container actions that require remote execution depend on valid FTP/SSH Access records.
  • If you see “Unable to find component … containers”, verify the enterprise module package is installed and autoloaded.
  • Use Scheduler + Task Queue pages to monitor queued infrastructure jobs.