- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
11-18-2024 04:24 PM
Hi All,
Cyberark sets the alias from docker to Podman when installing a new remote access connector.
Podman is installed. Setting alias docker=podman
Podman is installed. Setting alias docker=podman
################################################################################
Cyberark Remote Access Connector Installation
################################################################################
Validating os version...
Supported os version: Red Hat Enterprise Linux 8.10
DONE
Validating CPU SSE 4.2 compatibility...
DONE
Creating 'cyberark-remote-access' user...
User 'cyberark-remote-access' (uid: 369) already exists
DONE
Creating 'cyberark-remote-access' group...
Group 'cyberark-remote-access' (gid: 369) already exists
DONE
Creating docker network 'cyberark'...
Docker network 'cyberark' already exists
DONE
Updating environment variable 'PATH'...
DONE
Validating docker registries configuration file for registry 'docker.io/alerocyberark/connector:latest'...
Updating docker registries configuration file: '/etc/containers/registries.conf'
Restarting docker service...
Redirecting to /bin/systemctl restart docker.service
Failed to restart docker.service: Unit docker.service not found.
DONE
Login to docker hub (username: 'remoteaccessuser')...
Password:
Error: authenticating creds for "docker.io": pinging container registry registry-1.docker.io: Get "https://registry-1.docker.io/v2/"
For some reason alias is not getting set properly. I have podman.service but the restart doesnt work.
Am i missing something?
11-19-2024 02:50 AM
Hi @Froz Abdul Wahab Ameer Ahamed
Does your installation script directly refers to docker.service ?
If so it will fail because Podman uses podman.socket instead of a service.
Also please check that Verify your server can connect to Docker Hub (https://registry-1.docker.io).
Hope it helps !
11-28-2024 05:47 AM
Hi @Froz Abdul Wahab Ameer Ahamed
As the community has not yet provided an answer to this question for some time, were you able to find a solution?
If so, we'd appreciate it if you could share it. Your solution could help other community members who have similar questions.
Thanks, Liad.
11-29-2024 02:46 AM
Hi LiadD,
I was able to fix it as there where some issues with my proxy whitelisting. I installed and I was able to register the connector as well. It give a different error which we are investigating.
regards,
Froz
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!

