Examine SELinux logs and fix common violations in a click.

Spot and react to misbehaving virtual machines.

Write your own custom modules to make Cockpit do anything you wantĪlso troubleshoot and fix pesky problems with ease:.Extend Cockpit’s functionality by installing a growing list of apps and add-ons.Switch between multiple Cockpit servers.Use a terminal on a remote server in your local web browser.Inspect and interact with systemd-based services.

Manage storage (including RAID and LUKS partitions).

Here’s a subset of tasks you can perform on each host running Cockpit: ExtendableĬockpit also supports a large list of optional and third-party applications. It runs on demand, thanks to systemd socket activation. Network-wide logins are also supported through single-sign-on and other authentication techniques.Ĭockpit itself doesn’t eat resources or even run in the background when you’re not using it. It doesn’t reinvent subsystems or add a layer of its own tooling.īy default, Cockpit uses your system’s normal user logins and privileges. IntegratedĬockpit uses APIs that already exist on the system. Cockpit even has a built-in terminal, which is useful when you connect from a non-Linux device. You can switch back and forth between Cockpit and whatever else you like.

Keep using the command line, Ansible, and your other favorite tools and add Cockpit to the mix with no issues.Ĭockpit uses the same system tooling you would use from the command line. Have a favorite app or command line tool that you use on your servers?

Basically, you can think of Cockpit like a graphical “desktop interface”, but for individual servers. It’s easy to start containers, administer storage, configure networks, and inspect logs. See your server in a web browser and perform system tasks with a mouse. You don’t have to remember commands at a command-line.

Ubuntu fan speed