Pulse Server Podman Requirements

Introduced

Pulse supports installation using Podman starting from version 4.0.1.


Mode of Installation

Pulse provides two types of installation modes:


Docker Compatibility Matrix

The following table describes the compatibility matrix for various versions of Podman with Pulse.

Podman Version

Pulse Version

4.0.0 or above

4.0.1 or above


Podman

Only Pulse servers require a podman socket, and support is only accessible on certain operating systems, as specified in the official podman manual Podman Installation.


Pre-Requisites (VM/k8s)

Podman installation

  • Redhat Linux

yum install podman -y
  • Debian

apt install podman -y

Online Installation

Instructions to install Podman using this link: Podman Installation.

Commands to run:

sudo yum install podman -y systemctl enable --now podman.socket systemctl status podman.socket
Error

If the following error is being observed during accelo deploy corein debian based linux, update the Podman version from 3.x -> 4.x.

Cannot create the new container: 'ad-db_default'. Because: "specify container image platform" requires API version 1.41, but the Docker daemon API version is 1.40

Troubleshoot script:

  1. Before running this script, make sure to remove the unsupported Podman installation.

  2. Update the ubuntu_version respective to your ubuntu os version.

#!/bin/sh ubuntu_version='22.04' key_url="https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable/xUbuntu_${ubuntu_version}/Release.key" sources_url="https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable/xUbuntu_${ubuntu_version}" echo "deb $sources_url/ /" | tee /etc/apt/sources.list.d/devel:kubic:libcontainers:unstable.list curl -fsSL $key_url | gpg --dearmor | tee /etc/apt/trusted.gpg.d/devel_kubic_libcontainers_unstable.gpg > /dev/null apt update apt install podman
  1. Enable podman socket.

systemctl enable --now podman.socket
Info

Before proceeding, verify that the Podman socket is enabled. Without it, PulseManager/Accelo cannot connect to Podman.


Installation in VMs (Podman Socket Configuration)

When deploying databases on VMs during Pulse Kubernetes-based deployment, update the user configuration to allow the Podman socket to communicate with the databases for management operations.

  1. Change the systemd editor.

export SYSTEMD_EDITOR=vim
  1. Edit the systemd file for podman.sock.

systemctl edit podman.socket

Add the below content and save it.

[Socket] SocketUser=<Acceldata user> SocketGroup=podman SocketMode=0660

Offline Installation

Acceldata provides a link to download the offline RPM bundle for Podman CE binaries(only for RHEL/Ubuntu) along with the Pulse image tarball file, download these two files and unpack them on the Pulse server:

Steps to Install Podman from Offline RPM(s):

  • Unzip the Podman rpms on the Pulse server

  • Go to unzipped folder

  • Execute command: rpm -ivh ./*

  • Post above command gets completed, please validate with Podman version command.

Steps to Load Pulse Images on Podman:

  • Download all the container images (*.tgzfiles) and keep it inside the images directory.

  • Go to the images directory and run the following command.

ls -1 *.tgz | xargs --no-run-if-empty -L 1 podman load -i