-
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
errors with varlink via systemd #4005
Comments
I can reproduce immediately. Interestingly, I cannot reproduce when avoiding the socket activation and running |
|
Fix the logic when getting the runtime for varlink to actually disable SDNotify support. Fixes: containers#4005 Signed-off-by: Valentin Rothberg <[email protected]>
It looks like the logic to disable sdnotify was wrong. Opened #4089 to address the issue. It fixes the issues locally but lets wait what the CI has to say. |
Oh this is fantastic! Thanks @vrothberg 😺 |
/kind bug
Description
When executing in a tight loop, or multiple simultaneous podman-remote throws
EOF
errors.Steps to reproduce the issue:
make podman podman-remote
make install PREFIX=/usr
systemctl daemon-reload
systemctl enable io.podman.socket
systemctl enable io.podman.service
systemctl start io.podman.socket
while podman-remote run -it --rm alpine echo "hi"; do :; done
Describe the results you received:
Either:
or
Describe the results you expected:
A continuous stream of
hi
and no errors.Additional information you deem important (e.g. issue happens only occasionally):
Found while discovering/debugging issue #3998
Also sometimes reproducible with:
podman-remote run --rm alpine echo "hello" & podman-remote run --rm alpine echo "hello"
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):af8fedc
Additional environment details (AWS, VirtualBox, physical, etc.):
Reproduced on a VM with 2 vCPUs (no threads) and 4 GiB memory.
The text was updated successfully, but these errors were encountered: