RHEL Installer Type and Podman Installation Steps

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

RHEL Installer Type and Podman Installation Steps

L1 Bithead

1. What RHEL installer type (minimal or full fledge GUI) should be considered for XSOAR engine server?

 

2. Is there any documentation by Palo Alto on Podman proxy configuration for XSOAR Engine installation and any specific URLs required to be whitelisted for Podman like Docker? 

 

The following URL has information on Docker but not related to Podman.

https://docs.paloaltonetworks.com/cortex/cortex-xsoar/6-6/cortex-xsoar-install-guide/system-requirem...

 

Thank you 🙂

1 accepted solution

Accepted Solutions

L4 Transporter

Hi @gnakhede, the Engine does not require a GUI. You can use the minimal installation without GUI. You need to ensure that connectivity to a RHEL repo is available for package dependencies . For the list refer - https://docs.paloaltonetworks.com/cortex/cortex-xsoar/6-6/cortex-xsoar-install-guide/single-server-d...

 

Required URLs are the same for Docker and Podman since the images are pulled from the same location.

 

Use this documentation to configure the engine to use a proxy - https://docs.paloaltonetworks.com/cortex/cortex-xsoar/6-6/cortex-xsoar-admin/engines/configure-engin...

View solution in original post

3 REPLIES 3

L4 Transporter

Hi @gnakhede, the Engine does not require a GUI. You can use the minimal installation without GUI. You need to ensure that connectivity to a RHEL repo is available for package dependencies . For the list refer - https://docs.paloaltonetworks.com/cortex/cortex-xsoar/6-6/cortex-xsoar-install-guide/single-server-d...

 

Required URLs are the same for Docker and Podman since the images are pulled from the same location.

 

Use this documentation to configure the engine to use a proxy - https://docs.paloaltonetworks.com/cortex/cortex-xsoar/6-6/cortex-xsoar-admin/engines/configure-engin...

L1 Bithead

Hi @jfernandes1 Thank you for the quick response. Really appreciate it.

I just wanted to clarify my doubt regarding the proxy configuration for Podman.

On the below Red Hat website, they mentioned that Podman reads the environment variables for HTTP_PROXY information or can be configured under /etc/profile.d .
So will Podman be able to read the environment variables of  HTTP_PROXY information which I configured for the XSOAR engine which is given below by Palo Alto?
https://docs.paloaltonetworks.com/cortex/cortex-xsoar/6-6/cortex-xsoar-admin/engines/configure-engin...


https://access.redhat.com/solutions/3939131

Podman reads the environment variables for HTTP_PROXY information. HTTP_PROXY information should be configured as an environment variable for user running as podman or can be configured under /etc/profile.d

Example in /etc/profile.d/http_proxy.sh

export HTTP_PROXY=http://192.168.0.1:3128
export HTTPS_PROXY=http://192.168.0.1:3128

 

L4 Transporter

Hi @gnakhede,

No, for podman you will have to configure proxy on the environment. Once you configure the proxy you can test it with the below command. The proxy needs to configured either globally or for the demisto user account. 

 

The below should test both podman's connectivity to docker hub and the demisto user's ability to create containers. 

 

 

sudo -u demisto podman run --rm -t demisto/python3:3.10.4.29342 echo "podman is working"

 

 

  • 1 accepted solution
  • 1848 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!