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
Youki does not have reply from dbus #2559
Comments
Thanks for your report. May I ask you to build youki from the latest source code? I guess we have already fixed this bug 👍 |
Thank you for your reply. I built it from the main branch, and I was running rootful podman, for which I didn't find any similar issues. |
Also, I can't reproduce it every time. Sometimes, it gives an error message like this:
|
Hey @peter-jerry-ye , are you able to run podman rootless container with youki , or not at all? The channel connection broken error is probably a side effect of dbus error. I have seen this in CI a few times as well, but not able to reproduce it locally. |
@YJDoc2 Hi. Yes, I can run podman normally with youki unless it's a wasm workload. I think it is the wasm workload that causes the problem, but I couldn't find any addition error messages to help me locate the problem. |
@peter-jerry-ye while it is possible that it is specifically wasm workload that is causing the issues ; I feel this is a more general issue, as in our CI (where I have also seen this kind of failure) does not test wasm workload. Can I ask you to run non-wasm workloads in rootless mode in a loop for sometime, and see if that also fails? And would you be willing to share strace and dbus logs related to youki when such failure happens, so we might be able to understand this better? If you're fine with sharing them, I'll comment on commands to be run, and what exactly is to be collected. Thank you! |
I just retried another way. I built with |
@YJDoc2 No, I did not observe failure with non-wasm workloads. Could you please let me know the commands to be run? Thanks. |
Hey, so not sure why this would specifically happen for wasm workloads, but can you run the following commands and share the o/p? # podman create command with --runtime youki
strace -o ./strace.log -e '!futex' -x -v -s 2048 -f podman run <container_name>
The create command should be run normally, as podman does not call youki there ; running the strace + podman run should create a Apart from that another useful log would be of dbus messages itself, which can be seen by running The way I do this is to create two terminals, scale them so both are visible at same time and I don't need to switch windows ; try to keep any other programs running to minimum ; let the initial message flood for few seconds, and then running the podman command. That way the next messages should all be of youki itself. If you can share those logs as well, it wold be great! Thanks a lot! |
Hi, here's my strace.log. Though I think it reported a different error this time. |
@peter-jerry-ye For some reason, I cannot access the log file you have uploaded. It shows a 404 error when I open the link. Can you check / re-upload? Also can you tell what different error it was ? That would also help when going through the strace logs. Thank you! |
Hey @peter-jerry-ye , can you take a look at my previous comment? Thanks! |
@YJDoc2 Sorry, I had some health issue during the last few weeks. I'll reupload the strace. |
Hi, I'm trying to use youki to run wasm. I followed the tutorial, using the rootful podman + debug build of youki + feature wasmtime. However, I'm getting the following error:
What may be the cause of the error? Thank you.
The text was updated successfully, but these errors were encountered: