Guide

Docker logs in the browser

The docker logs command is fine for one container on one host. When you're reading a busy container during an incident, or the container is on another machine, a browser view with search and colours is faster. Here's both.

Updated , for FleetOps v1.4.1.

Without a UI

Good for a quick look on the host itself.

docker logs prints what the container wrote to stdout and stderr. -f follows it, --tail limits how far back it starts, and --since and --timestamps help when you're matching logs to an incident time:

docker logs
docker logs -f --tail 200 my-container
docker logs --since 30m --timestamps my-container
docker compose logs -f --tail 100

The limits show up under pressure: the terminal scrollback fills, there's no search beyond piping through grep, colour codes get mangled, and you need a shell on the right host for each container.

In the browser with FleetOps

Every container's Logs tab, on every host you manage.

  • Big logs stay fast. The viewer is virtualized and keeps the newest 200,000 lines.
  • Search. Plain text or a regular expression, with matches highlighted.
  • Filters. Show stdout, stderr or both, with or without timestamps, from the tail or a time range.
  • Colours. ANSI colour codes render as colours, not escape sequences.
  • No repeats. After a reconnect or a container restart, the view resumes where it stopped.
  • Download the log to attach to a ticket.

The same viewer shows a Docker Swarm service's logs across its tasks, and a Kubernetes workload's logs merged across its pods.

Start it

Run FleetOps
docker run -d --name fleetops -p 9000:9000 \
  -v fleetops-data:/data \
  -v /var/run/docker.sock:/var/run/docker.sock \
  --group-add "$(docker run --rm -v /var/run/docker.sock:/s busybox:1.37 stat -c %g /s)" \
  fleets/fleetops

Open http://localhost:9000, create the admin account, then pick a container and open Logs. Teammates can get a viewer role, which reads logs without changing anything, and terminal sessions are recorded in the audit log.

If logs are all you need, a dedicated read-only log viewer is lighter still. FleetOps makes sense when you also want to restart the container, open a shell or roll back a stack from the same screen.

Questions

How do I view Docker container logs in a web browser?

Run a web UI that reads the Docker socket, such as FleetOps, and open the container's Logs tab. FleetOps streams the logs live, keeps the newest 200,000 lines, and lets you search them with text or a regular expression.

Can I search Docker logs in the browser?

Yes. FleetOps searches the loaded lines with plain text or a regular expression and highlights the matches, and can show only stdout or only stderr.

What happens to the log view when the connection drops?

FleetOps resumes from where it stopped when the connection comes back or the container restarts, without repeating lines it already showed.

Can I see logs from containers on other hosts?

Yes. Remote Docker hosts join FleetOps through an agent that dials out, so their logs open in the same browser tab without exposing the Docker API on the network.

Read next