Menu ▾ ▴

Docker Containers

sanjaya danushka

Docker Containers

Pull, run, stop, and clean containers — with port mappings, volumes, environment, and GPU passthrough from a GUI screen.

Overview

Screenshot_20260910_203323

The Docker page manages containers and images on your machine through Docker. It wraps the container workflow into visible actions, so you can spin up services without remembering the CLI flags.

  • Pull — pull an image by name.
  • Run — create and start a container with your options.
  • Stop / start — toggle running state.
  • Clean — remove stopped containers and unused images.

1. Search & Run Container

Screenshot_20260910_203156

The top-right header has a search box to filter containers by name, and a green Run Container button to create and start a new container.

2. Overview cards

Screenshot_20260910_203214

Four stat cards sit below the header:

Card What it shows
Containers Total containers on the system
Running Containers currently running
Images Docker images available locally
Storage Total disk space used by Docker

3. Tabs

Four tabs sit below the stat cards:

Containers

Screenshot_20260910_203238

Lists all containers with status (Running / Exited), image name, and uptime. Each row has Stop / Start and Remove buttons.

Images

Screenshot_20260910_203248

Lists all local Docker images with tag, size, and creation date. Each row has a Remove button. Use the search box to filter by image name.

Volumes

Screenshot_20260910_203256

Lists Docker volumes with name, mount point, and driver. Each row has a Remove button.

Networks

Screenshot_20260910_203256-1

Lists Docker networks with name, driver, and scope. Each row has a Remove button for user-created networks.

Options when running a container

Screenshot_20260910_203238

Option What it does
Image Select the image to run (e.g. postgres:16-alpine)
Container name Give the container a friendly name
Port mappings Expose container ports to the host (host:container)
Volumes Mount host directories into the container
Environment Set environment variables passed to the container
GPU passthrough Enable GPU access for containers that need it
Restart policy Choose restart behavior (e.g. always, unless-stopped)

How to use

  1. Pull an image — use the Run Container dialog or pull via CLI to get an image.
  2. Run — pick the image, configure ports/volumes/env/GPU, set the restart policy, and start.
  3. Manage — stop/start running containers, inspect them, clean up when done.
  4. Clean — remove stopped containers and dangling images to reclaim space.

Good to know

  • NeoArch talks to the Docker daemon the same way docker does — make sure the Docker service is running (systemctl start docker).
  • Container config (ports, volumes, env) is per-run: changing an option means recreating the container.
  • "Clean" only removes containers/images you choose — it never touches running containers.
  • Use the search box to quickly filter long lists across any tab.

↩ Back to Home


Related

Wiki: AppImages
Wiki: Home