What the Docker widget provides

The Docker Engine widget connects to the Docker API through the HomeStart server. It can show containers, images, volumes and networks, container resource activity, health and restart information, inspection details and logs. Each widget instance can remember a different selected Docker engine.

Before connecting

Good to know
  • Use a private LAN or Tailscale address that the HomeStart server can reach.
  • Give every engine a clear name such as Ubuntu Docker, Media Server or Production Containers.
  • Prefer a TLS-protected Docker endpoint or a tightly controlled private proxy.
  • Never expose an unauthenticated Docker API port to the public internet: Docker API access can provide control of the entire host.

Add the first engine

  1. Add the Docker Engine widget to a Homelab page.
  2. Choose Configure or Add engine.
  3. Enter a recognisable engine name.
  4. Enter the complete endpoint, including http:// or https:// and its port.
  5. Add the required protected credential when your proxy or endpoint uses one.
  6. Choose Save & test connection.
  7. Confirm Docker online appears and the resource counts load.

Add another Docker system

  1. Choose + Engine beside the engine selector.
  2. Enter the second system’s name and endpoint.
  3. Save and wait for the status check to complete.
  4. Use the selector above the resource tabs to switch engines.
  5. Add another Docker widget when you want two engines visible at the same time; select a different engine in each widget.

Edit, cancel or remove an engine

Open Configure to change the selected engine’s name, address or credential. Closing an unsaved new-engine form discards only that draft and keeps the existing engine selected. Use Remove only after checking the displayed engine name and address. Removing a HomeStart connection does not stop Docker or delete containers, images, volumes or networks on the host.

Understand the resource tabs

Good to know
  • Containers are running or stopped instances created from images.
  • Images are reusable application templates used to create containers.
  • Volumes keep persistent application data outside a container’s writable layer.
  • Networks control how containers communicate with each other and other systems.

Logs and inspection

Open logs from a container row to use the wide log viewer. Choose a suitable line count, scroll inside the viewer, and copy or download logs when needed. Inspection details can contain environment values, so HomeStart masks common secret fields; still treat exported details and logs as sensitive.

If the engine is offline or times out

  1. Confirm Docker is running on the remote host.
  2. Confirm the endpoint is listening on the expected private address and port.
  3. Test the address from the HomeStart server, not only from your laptop.
  4. Check the host firewall, VPN route and reverse-proxy rules.
  5. Verify TLS certificates and credentials when HTTPS or authentication is enabled.
  6. Do not solve a timeout by opening an unauthenticated Docker port to the public internet.

Final checks

Good to know
  • Refresh HomeStart and confirm the selected engine is remembered.
  • Switch between every saved engine and verify that their names and counts differ as expected.
  • Check compact, standard, wide and full-width widget sizes.
  • Use a theme with both light and dark surfaces to confirm labels and controls remain readable.