If you do not use SSH keys, you are prompted with each Podman command for your login password. On a Mac, you can automate this using ssh-copy-id. You need to copy the contents of id_rsa.pub and append it to ~/.ssh/authorized_keys on the Linux server. To set up your SSH connection, you need to generate an SSH key pair by using the ssh-keygen command: $ ssh-keygenīy default, the public key is in your home directory under. The remote client works considerably smoother with SSH keys. Remote Podman uses SSH to communicate between the client and the server. If it is not currently enabled, use the following command: $ sudo systemctl enable -s sshd Set up SSH Package: conmon-2.0.86_64 Enable sshdįor the client to communicate with the server, you need to enable and start the SSH daemon on your Linux machine. Verify that the socket is listening with the following simple Podman command: $ podman -remote info You need to enable linger for this user for the socket to work when the user is not logged in.

You enable this socket permanently using the following command: $ systemctl -user enable podman.socket By default, the rootless socket listens at /run/user/$/podman/podman.sock. In these examples, we run Podman as a normal, unprivileged user (also known as a rootless user). Install Podman using this command: $ brew install podman Create the first connection Enable the Podman service on the serverīefore performing any Podman client commands, you must enable the podman.sock systemd service on the Linux server. You can download Homebrew via the instructions on their site. The Mac client is available through Homebrew. Podman must be run at a command prompt using the Windows cmd.exe or PowerShell applications. The installer puts podman in the default user path. Once you have downloaded the installer, simply double-click it, and Podman client is installed.

Remote for mac service not available