HostCritiq
Search ⌘K
Menu

Application hosting

Hosting Dozzle

Dozzle brings container logs and resource information into a browser. It is useful when several services run on one host, or when checking a failure means jumping between multiple machines. You can follow logs together, filter messages and inspect container activity from the same screen. Optional container actions and shell access add more control, but also make access permissions especially important.

Requirements last checked against the project's documentation.

Compare server plans Size a server

Understand the setup

Find the software and services needed to run the application.

See requirements

Budget your resources

Plan memory, storage and CPU for the way you will use it.

Open resource planner

Build your shortlist

Compare plans for the starting size, then review the provider and billing terms.

See plans

Must have

Installation requirements

  • Docker Engine 19.03 or later with API 1.40 or later for the Docker setup.
  • Access to the intended container runtime or a configured remote agent.
  • Persistent storage for Dozzle settings when using the container setup.

Recommended

Planning guidance

Use the resource planner to size a server for your workload.

Choosing a server for Dozzle

Log volume, the number of connected containers and simultaneous viewers affect the workload. Begin with the services you actually need to inspect and watch resource use before connecting a much larger fleet.

Deploy with

Supported paths

  • Docker container
  • Docker Compose
  • Docker Swarm
  • Kubernetes

The host must provide

Runtime

Container runtime
Docker Engine 19.03+ for Docker deployments; use a maintained release.

Storage

Persistent data

Persist the settings directory separately from the container. Size and rotate application logs at the container runtime as well; a log viewer does not replace a deliberate retention policy.

Step by step

Plan your Dozzle deployment

  1. Connect the intended host

    Deploy the official container with access to the runtime and persistent settings.

    Official instructions
  2. Restrict access

    Configure authentication and HTTPS before making the interface reachable outside the trusted network.

    Official instructions
  3. Add remote hosts deliberately

    Use the documented agents for additional hosts and limit administrative capabilities to the people who need them.

    Official instructions

Security

Before you go public

  • Docker socket access is effectively administrative access to the host. Treat the Dozzle service and its users accordingly.
  • Leave shell and container-changing actions disabled unless there is a clear operational need.

Cost

Beyond the server price

  • The self-hosted application is MIT licensed; hosting and retained container logs still consume resources.
  • Dozzle Cloud is an optional separate service, rather than a prerequisite for viewing local container logs.

Want the full monthly bill? Use the hosting cost calculator. Add storage, backups and other costs to your estimate.