Red Hat and Podman Configuration - Netskope Technical Documentation

This document provides help regarding deployment and configuration of Event Streaming Client on Red Hat with podman.

Podman is the default container manager provided by Red Hat.

To verify if a Linux is using docker or podman use docker --version command:

docker --version
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
podman version 5.6.0

Deploying on Red Hat with Podman

Only rootless deployment is supported on Red Hat with podman:

Subordinate UID/GID mappings must be configured
Enable User Lingering
python installer must be executed without root account or sudo

Configure Subordinate UID/GID Mappings

Subordinate UID/GID allows to map UID/GID of the container to dedicated UID/GID on the host to increase security.

Edit of Subordinate UID/GID requires root privilege.

To view the current mapping, check the files /etc/subuid and /etc/subgid:

$ cat /etc/subuid
matt:100000:65536
$ cat /etc/subgid
matt:100000:65536

The line matt:100000:65536 defines the following configuration

matt: the user name
100000 (Start ID): This is the beginning of the range of UIDs/GIDs assigned to the user. The container’s internal root user (UID 0) will be mapped to this ID on the host system.
65536 (ID Count): This is the total number of sequential IDs allocated for the user’s rootless containers (e.g., UIDs $100000$ through $165535$). This large block ensures containers have enough unique IDs for all their internal users and processes.

If the user running the container is already defined, Subordinate UID/GID are properly configured.

In case the Subordinate UID/GID is missing, it can be added with the following command:

# Add subordinate UID mapping for your user
echo "$USER:100000:65536" | sudo tee -a /etc/subuid

# Add subordinate GID mapping for your user
echo "$USER:100000:65536" | sudo tee -a /etc/subgid

Change the Start ID to allocate a free range for the user added.

Verify the content of the files after editing it.

To apply the new mapping, run the following command:

podman system migrate

Enable User Lingering

User Lingering is mandatory to allow the user to execute a command without having an active session.

sudo loginctl enable-linger $USER

Run the installer

Execute with a regular user without sudo:

$ python netskope_event_streamingclient_installer.py
NETSKOPE LOG STREAM CLIENT INSTALLER I.2025.12.1

Please specify an option:
1. install          - Set up and configure the container
2. reinstall        - Remove and recreate the container
3. uninstall        - Remove the container and cleanup
4. update_client_key - Update client key and restart container

Enter option (install/reinstall/uninstall/update_client_key):

HTTP Proxy

If HTTP proxy is required , proxy entry is also needed in ~/.config/containers/containers.conf. if either the file is not present or the proxy entry is not present, make the proxy entry in file ~/.config/containers/containers.conf :

[engine]
env = [
    "HTTP_PROXY=http://163.xxx.xxx.80:80",
    "HTTPS_PROXY=http://163.xxx.xxx.80:80"
]