-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User socket events endpoint returns error 500 #9993
Comments
Can you do a |
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 |
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 |
Does this file exist by default? |
Depends on the packaging. If it does not exists you can copy it from |
It works by setting |
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 |
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
The text was updated successfully, but these errors were encountered: