"502 Bad Gateway" if I switch to the krun runtime #28551
Replies: 3 comments 6 replies
-
|
@jakecorrenti @slp Does krun not accept incoming connecting to the container ip? I am not sure how the networking via krun in general works because it does not seem to have any (non localhost) interface or any routes in the container so I am a bit confused. and pings all fail with |
Beta Was this translation helpful? Give feedback.
-
|
Hello again, it's been a few days and I still haven't received a reply. I tried a few other things, like switching between pasta and slirp4netns, but it still didn't work. Can anyone help me? Should I open an issue? |
Beta Was this translation helpful? Give feedback.
-
|
Hi! libkrun maintainer here. Thanks for the detailed report. I've tested this on my machine, and found ngnix failing with this error: This happens because TSI doesn't support FIONREAD/SIOCINQ yet. But, luckily, can be easily supported. I'm preparing a PR for libkrunfw, will link it here once it's ready. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm going crazy trying to get this simple setup to work with krun. It works fine with crun, but as soon as I switch runtime (setting
/etc/containers/containers.conf), I get a502 Bad Gatewayerror.The containers start up correctly but are effectively unusable. I've tried this on two different operating systems (Manjaro and Arch Linux).
demo.nework:
redlib.container:
nginx.container:
nginx.conf:
As I said, it must be krun's fault, because everything works fine without it.
(obviously, I don't want to use crun)
Beta Was this translation helpful? Give feedback.
All reactions