Manage Podman Containers Using Cockpit on RHEL

Perform the following:

1. Install the container-tools application stream.

2. Install cockpit.

3. Use enable and start the cockpit.socket socket using systemctl.

4. Now we can connect to the Cockpit web console on port 9090. Let's log in as cloud_user.

5. You'll notice that we get a message that the "Podman service is not active." Let's start it.

Now that we're good to go, we see that we have no containers or images. Let's change that!

Connect to the Cockpit web console. Let's log in as cloud_user.

Let's take a look at the tab for the Podman containers plugin.

You'll notice that we get a message that the "Podman service is not active." Let's start it.

First, let's grab some images. We'll grab the following:

• wordpress (from docker.io/library/wordpress)
• mariadb (from docker.io/library/mariadb)

Let's use our images to start some containers!

We're going to start a WordPress installation, using two containers:

Start a mariadb container:

• Name the container wp-db.
• Publish port 3306 in the container to port 3306 on the host.
• Use the mariadb container image.
• Set the following variables:
  • MYSQL_ROOT_PASSWORD="dbpass"
  • MYSQL_DATABASE="wp"
  • MYSQL_USER="wordpress"
  • MYSQL_PASSWORD="wppass"

Start a WordPress container:

• Name the container wp-web.
• Publish port 80 in the container to port 8080 on the host.
• Use the wordpress container image.
• Set the following variables:
  • WORDPRESS_DB_NAME="wp"
  • WORDPRESS_DB_USER="wordpress"
  • WORDPRESS_DB_PASSWORD="wppass"
  • WORDPRESS_DB_HOST="enter the private IP address of host"

Now that our containers are up and running, let's test them!

Let's try connecting to our WordPress installation using the external DNS or IP address of our server and port 8080.

You should get the WordPress setup page. When you're done testing, clean up all the containers and images.

Great work, Cloud Guru! You stood up a WordPress instance using Cockpit and the Podman plugin!