Base de connaissances

If you already have Cockpit on your server, point your web browser to: https://ip-address-of-machine:9090

Use your system user account and password to log in. See the guide for more info.

After installing Cockpit itself, consider installing additional applications in Cockpit.

Red Hat Enterprise Linux

Cockpit is available in Red Hat Enterprise Linux 7 and later.

1. On RHEL 7, enable the Extras repository.

   sudo subscription-manager repos --enable rhel-7-server-extras-rpms
   

   RHEL 8 does not need any non-default repositories.

2. Install cockpit:

   sudo yum install cockpit
   

3. Enable cockpit:

   sudo systemctl enable --now cockpit.socket
   

4. On RHEL 7, or if you use non-default zones on RHEL 8, open the firewall:

   sudo firewall-cmd --add-service=cockpit
   sudo firewall-cmd --add-service=cockpit --permanent
   

Fedora CoreOS

The standard Fedora CoreOS image does not contain Cockpit packages.

1. Install Cockpit packages as overlay RPMs:

   rpm-ostree install cockpit-system cockpit-ostree cockpit-podman
   

   Depending on your configuration, you may want to use other cockpit-* extensions as well, such as cockpit-kdump or cockpit-networkmanager.

   If you have a custom-built OSTree, simply include the same packages in your build.

2. Reboot

Steps 1 and 2 are enough when the CoreOS machine is only connected to through another host running Cockpit.

If you want to also run a web server to log in directly on the CoreOS host:

1. Enable password based SSH logins, unless you only use SSO logins:

   echo 'PasswordAuthentication yes' | sudo tee /etc/ssh/sshd_config.d/02-enable-passwords.conf
   sudo systemctl try-restart sshd
   

2. Run the Cockpit web service with a privileged container (as root):

   podman container runlabel --name cockpit-ws RUN quay.io/cockpit/ws
   

3. Make Cockpit start on boot:

   podman container runlabel INSTALL quay.io/cockpit/ws
   systemctl enable cockpit.service
   

Afterward, use a web browser to log into port 9090 on your host IP address as usual.

CentOS

Cockpit is available in CentOS 7 and later:

1. Install cockpit:

   sudo yum install cockpit
   

2. Enable cockpit:

   sudo systemctl enable --now cockpit.socket
   

3. Open the firewall if necessary:

   sudo firewall-cmd --permanent --zone=public --add-service=cockpit
   sudo firewall-cmd --reload
   

Debian

These commands require a POSIX compatible shell like bash. For other shells like fish, temporarily run bash -i.

Cockpit is available in Debian since version 10 (Buster).

1. To get the latest version, we recommend to enable the backports repository (as root):

   . /etc/os-release
   echo "deb http://deb.debian.org/debian ${VERSION_CODENAME}-backports main" > \
       /etc/apt/sources.list.d/backports.list
   apt update
   

2. Install or update the package:

   apt install -t ${VERSION_CODENAME}-backports cockpit
   

When updating Cockpit-related packages and any dependencies, make sure to use -t ...-backports as above, so backports are included.

Ubuntu

These commands require a POSIX compatible shell like bash. For other shells like fish, temporarily run bash -i.

Cockpit is available in Ubuntu 17.04 and later, and available as an official backport for 16.04 LTS and later.

We recommend installing or updating the latest version from backports. This repository is enabled by default, but if you customized apt sources you might need to enable them manually.

. /etc/os-release
sudo apt install -t ${VERSION_CODENAME}-backports cockpit

On Linux Mint, use UBUNTU_CODENAME instead of VERSION_CODENAME like so:

sudo apt install -t ${UBUNTU_CODENAME}-backports cockpit

When updating Cockpit-related packages and any dependencies, make sure to use -t ...-backports as above, so backports are included.

Arch Linux

Cockpit is available in Arch Linux:

sudo pacman -S cockpit
sudo systemctl enable --now cockpit.socket

If the first command fails with “database file for … does not exist”, refresh/update your system with sudo pacman -Syu first.