Pulse Server Podman Requirements

Mode of Installation

Pulse provides two types of installation modes:

• Online Installation: The Pulse server must have direct or proxy access to the internet to pull Pulse packages.
• Offline Installation: In this route, the user must whitelist the following URLs and complete the offline Pulse-based installation.
  • https://191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/*
  • https://accelo-binaries.s3-us-west-1.amazonaws.com/*

Podman Compatibility Matrix

For details about the compatibility matrix for various versions of Podman with Pulse, see Compatibility Matrix.

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

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

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