From ba8a71f9ce413fadb80f3fd1c063a9613987eed7 Mon Sep 17 00:00:00 2001 From: Benjamin Porter Date: Thu, 12 Nov 2020 15:28:25 -0700 Subject: [PATCH] Add missing --now in systemctl start command If you don't use --now or also run systemctl --user start podman.socket then the socket won't start until a reboot. Much easier to just start the socket at the same time as enabling it. Signed-off-by: Benjamin Porter --- docs/tutorials/mac_win_client.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tutorials/mac_win_client.md b/docs/tutorials/mac_win_client.md index 63830a5b1631..9e0798bbf89c 100644 --- a/docs/tutorials/mac_win_client.md +++ b/docs/tutorials/mac_win_client.md @@ -29,9 +29,9 @@ $ brew install podman ### Enable the Podman service on the server machine. -Before performing any Podman client commands, you must enable the podman.sock SystemD service on the Linux server. In these examples, we are running Podman as a normal, unprivileged user, also known as a rootless user. By default, the rootless socket listens at `/run/user/${UID}/podman/podman.sock`. You can enable this socket, permanently using the following command: +Before performing any Podman client commands, you must enable the podman.sock SystemD service on the Linux server. In these examples, we are running Podman as a normal, unprivileged user, also known as a rootless user. By default, the rootless socket listens at `/run/user/${UID}/podman/podman.sock`. You can enable and start this socket permanently, using the following commands: ``` -$ systemctl --user enable podman.socket +$ systemctl --user enable --now podman.socket ``` You will need to enable linger for this user in order for the socket to work when the user is not logged in.