This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-07
Channels
- # aleph (4)
- # announcements (9)
- # babashka (44)
- # beginners (6)
- # cider (8)
- # clj-kondo (5)
- # clojars (10)
- # clojure (10)
- # clojure-berlin (1)
- # clojure-dev (9)
- # clojure-europe (20)
- # clojure-gamedev (1)
- # clojure-miami (2)
- # clojure-nl (1)
- # clojure-norway (21)
- # clojure-uk (5)
- # clojurescript (12)
- # conjure (1)
- # cursive (19)
- # data-science (2)
- # datahike (10)
- # etaoin (5)
- # events (3)
- # fulcro (14)
- # gratitude (2)
- # honeysql (8)
- # humbleui (1)
- # hyperfiddle (60)
- # introduce-yourself (7)
- # jobs-discuss (27)
- # juxt (2)
- # kaocha (7)
- # lsp (23)
- # malli (9)
- # missionary (2)
- # off-topic (48)
- # pathom (24)
- # releases (1)
- # shadow-cljs (256)
- # sql (46)
- # xtdb (19)
Attempting to set :transport :io-uring
results in a "failed to create io_uring ring fd: Operation not permitted" in a containerized environment.
It's not a priority considering https://github.com/containerd/containerd/pull/9320
In theory, it's just a matter of setting the ':io-uring' keyword as transport (exactly what you have done ). Everything else is transparent and should continue to behave the same inside your application (even inside the Aleph code-base). I'm no IO Uring expert but there might be good explanation about why IO Uring cannot be used inside some containers environment. Probably documented and explained on some Netty issues.
☝️ 1