I run a few Docker containers on a small server. Every time something felt off, it was the same routine:
ssh me@server docker ps -a # Restarting (1) 12 seconds ago. Again? docker logs --tail 50 app # scroll, squint nano compose.yml # which port was it? docker compose up -d # did it work?
Enter fullscreen mode
Exit fullscreen mode
Five commands to answer three questions: is everything up, what broke, and why?
So I built Server Explorer , a calm web UI that sits on top of Docker and Compose. It doesn't replace them: everything it shows comes from Docker's API, deploys run the real docker compose up , and the stacks it creates are plain compose.yml files.
Small on purpose
Whoever controls Docker controls the whole server, so I kept the attack surface tiny. It only listens on 127.0.0.1 and is reached through an SSH tunnel, never from the network.…