Live data from Hacker News

Cockpit is a web-based graphical interface for servers

github.com

21–30 of 188 posts

Re: Cockpit is a web-based graphical interface for servers

#22
post #18

I tried using this to handle my 10-ish Docker containers, but I ended up using Portainer. Sure, not the same thing, but if someone (like me) thought Cockpit might be nice for managing a small Docker host, this didn't work for me

Going for a shameless plug - I am working on an observability dashboard for Docker Swarm: https://github.com/Radiergummi/cetacean

Also works for a single node cluster. Maybe that’s closer to what you’re looking for.

Re: Cockpit is a web-based graphical interface for servers

#24
I had a bad experience with it. We hired a contractor and he

1. insisted on a pre-war version of ubuntu

2. insisted on the cockpit. So you no longer can modify the NFS exports over ssh, you need to connect to this HTTP abomination. Very nice. Always wanted to open more ports on my servers

Re: Cockpit is a web-based graphical interface for servers

#27
post #26

What is the use case for this over standard command line tools like systemctl, journalctl, top, docker ps?

Web UIs are nicer to deal with for simpler tasks. You can use this on your phone easily. Less technical users can be instructed on how to perform simple tasks like remotely powering off a machine.

Re: Cockpit is a web-based graphical interface for servers

#29

I had a bad experience with it. We hired a contractor and he 1. insisted on a pre-war version of ubuntu 2. insisted on the cockpit. So you no longer can modify the NFS exports over ssh, you need to connect to this HTTP abomination. Very nice. Always wanted to open more ports on my servers

Sounds like you had a bad experience with a contractor.

Re: Cockpit is a web-based graphical interface for servers

#30

I've used this before in the early days of my Linux SysAdmin work, especially in the homelab. It's pretty solid , but the limited amount of projects and lack of visibility into the CLI it uses on the backend hinder the ability to translate sysadmin work into tangible Linux skills, so I dumped it at home in favor of straight SSH sessions and some TUI stuff. That said, if I gotta babysit Linux in an Enterprise without…

Part of the technical assessment I have for hiring new platform engineers involves troubleshooting a service hosted in a headless Linux vm.

Troubleshooting and fluency on the command line are among what I consider core skills. Being able to dig through abstraction layers is not just essential for when things go wrong, they are essential for building infrastructure, and really tells you whether an architecture is fit for purpose.

Post reply on HN