podman.socket is masked #17652
Answered
by
Luap99
zakaria-chahboun
asked this question in
Q&A
podman.socket is masked
#17652
-
I want to connect pods app with podman socket, I did this: systemctl enable --now --user podman.socket I got:
Then i did: sudo systemctl enable --now podman.socket I got:
Feb 28 12:22:27 geo sudo[18504]: pam_unix(sudo:session): session closed for user root
Feb 28 12:22:36 geo sudo[18543]: zaki : TTY=pts/1 ; PWD=/home/zaki ; USER=root ; COMMAND=/usr/bin/systemctl enable --now podman.socket
Feb 28 12:22:36 geo sudo[18543]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Feb 28 12:22:36 geo systemd[1]: Reloading.
Feb 28 12:22:36 geo systemd[1]: podman.socket: Socket service podman.service not loaded, refusing.
Feb 28 12:22:36 geo systemd[1]: Failed to listen on Podman API Socket. Any solution for this issue? Thanks 🌹 I have |
Beta Was this translation helpful? Give feedback.
Answered by
Luap99
Feb 28, 2023
Replies: 1 comment 2 replies
-
systemd units should not be masked by default so this likely something you did. You may want to also check that your units match our upstream ones: https://github.com/containers/podman/tree/main/contrib/systemd/system |
Beta Was this translation helpful? Give feedback.
2 replies
Answer selected by
zakaria-chahboun
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
systemd units should not be masked by default so this likely something you did.
To unmask a unit use
systemctl unmask ...
You may want to also check that your units match our upstream ones: https://github.com/containers/podman/tree/main/contrib/systemd/system