Closed bertmelis closed 3 years ago
Can you do a podman pull alpine
for example and try again. I think the problem is that you don't have any podman events in the journal.
Doesn't change.
Mind that it returns an error, it doesn't stay empty. As I understand it should "hang" waiting for something to show but it immediately returns with the error.
Do see anything in journalctl --user SYSLOG_IDENTIFIER=podman
?
Should this be done with 'sudo' or without? Because without I don't have sufficient permissions. And with sudo the journal is empty.
I do have a few (rootless) containers running and they are running fine.
This should work as rootless. podman events uses the journald backend by default. Your user has apparently no enough permissions to use it. I recommend changing the events_logger
to file
in /etc/containers/containers.conf
Does this file exist by default?
Depends on the packaging. If it does not exists you can copy it from /usr/share/containers/containers.conf
to this location.
It works by setting events_logger
to file
. I'll close the issue for now. Is there anything that can be done to make it work out-of-the-box?
Any chance you can try again with 3.1.0? @ashley-cui did a lot of fixes to the journald backend for that release.
3.1 cannot fix this when journalctl --user SYSLOG_IDENTIFIER=podman
does not work rootless. This is a distro specific configuration problem.
Any chance you can try again with 3.1.0? @ashley-cui did a lot of fixes to the journald backend for that release.
I'm inclined to say no, as 3.1.0 is not in the Kubik project's repo.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description I'm using Debian 10 with podman from the Kubik project as outlined in the podman documentation: https://podman.io/getting-started/installation.
The user events socket endpoint returns error 500:
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected: The command to wait for events.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes/NoAdditional environment details (AWS, VirtualBox, physical, etc.): physical