Skip to content

Docker Apps

François Côte edited this page Nov 22, 2026 · 3 revisions

Docker Apps

Docker lets you run small, ready-made applications on the NAS — things like a photo gallery, a media server, or a download manager — without installing anything by hand. Each application runs in its own self-contained container, separate from the rest of the system.

The Docker icon on the desktop only appears once Docker is installed and running. Its window has a menu down the left side with four sections — Containers, Images, Stacks and Volumes and networks — and the section you pick is shown on the right. If the window is made narrow, the menu shrinks to icons only.

Docker status and the service

The Docker page of the window shows whether Docker is running and which version it is. From there you can:

  • Restart the service — useful if Docker misbehaves. Running containers restart with it if they are set to do so.
  • Stop the service — asks you to confirm first, because every running container stops with it and the other Docker sections stay unavailable until you start it again.
  • Start the service — shown instead of the two buttons above when Docker is installed but not running.

Key ideas, kept simple

  • Images are the installable "packages" for applications — think of an image as the installer for a container.
  • Containers are running (or stopped) copies of an image — the actual applications.
  • Stacks are groups of containers that are meant to run together as one application.
  • Volumes and networks are how containers store files persistently and talk to each other and to the network; you'll rarely need to touch these directly unless an application's instructions ask you to.

Looking at a container

Each container is a row you can expand. The collapsed row shows its name, image, state, processor and memory use. Expanded, it also shows:

  • the ports it publishes to the NAS (if it publishes none, the page tells you to reach it by its IP address);
  • for each network it is connected to: the network name, its IP address, the gateway and the MAC address (and the IPv6 address if it has one). A stopped container has no address yet and shows --;
  • the buttons to Stop, Restart, Edit, see the Logs or Delete it.

Creating or editing a container

The container dialog is split into collapsible sections; only one is open at a time:

  1. Settings — the image, the name, the network and the restart policy.
  2. Ports — which port of the NAS leads to which port of the container.
  3. Environment variables
  4. Storage locations — NAS folders or Docker volumes mapped inside the container.
  5. Capabilities — the Linux rights granted to the container.

Volumes and networks

This section has two tabs, Volumes and Networks.

Networks

In the Networks tab, the list works the same way: click a network to expand it and see its subnet, gateway, IP range, IPv6, the containers connected to it, and a Delete network button. The networks Docker creates itself (bridge, host, none) cannot be deleted.

Create a network asks for:

  • a name;
  • a driver:
    • Bridge — a private network inside the NAS. Containers get their addresses from it, and you publish ports to reach them. This is what you want most of the time.
    • Macvlan — gives each container its own address on your real network, as if it were a separate machine. You choose the network interface of the NAS to attach it to and a mode (Bridge, Private, VEPA or Passthru).
    • IPvlan — like Macvlan, but containers share the NAS's hardware address. You choose the interface and a mode (L2 or L3).
  • a subnet (for example 172.20.0.0/16), a gateway and an IP range, all optional for Bridge. Macvlan and IPvlan need a subnet that matches your real network.
  • whether to enable IPv6.

Good to know: with Macvlan and IPvlan, the NAS itself cannot reach its own containers through the interface they are attached to — this is how Linux works, not a fault. Reach them from another computer on the network instead.

A folder a container uses

If a container needs access to your files (for example, a media server reading your video folder), point it at the folder when you set it up. Keep in mind: a container that reads a NAS folder has full access to it, regardless of the permissions you've set up for people connecting to that share — permissions only apply to network connections, not to containers running on the NAS itself.

Clone this wiki locally