Having trouble deploying and using Tigerbeetle -- needs io_uring
dyc3
PROOP

2 years ago

I'm deploying a service that uses Tigerbeetle to handle tracking financial transactions.

However, when I try to run my service that uses the tigerbeetle client, I get:

error(tb_client_context): 49360072845773278101607755070886542750: failed to initialize IO: SystemOutdated

Tigerbeetle uses io_uring exclusively for networking for performance reasons. I'm pretty sure that this is what it's complaining about, because io_uring is only available on Linux 5.5 and later.

Is io_uring available on Railway?

4 Replies

2 years ago

I've just checked and the kernel version in use is 6.1.0


dyc3
PROOP

2 years ago

Thanks for the quick reply! I went and looked up the code that is actually throwing this error: https://github.com/tigerbeetle/tigerbeetle/blob/3cd7cf4799f65c81ffbc36eda788b8b26fd7da72/src/io/linux.zig#L69

The full error message (which didn't show up in my logs for some reason) indicates that `seccomp` is disabling the io_uring syscalls. Tigerbeetle's docs for running in docker containers apply the `--security-opt seccomp=unconfined` argument, which makes those syscalls available. Is it possible to configure my service so those syscalls are available?


2 years ago

Sorry but we don't provide a way to change any security_opt configurations.


2 days ago

Any progress/update on the adding support for the modifying the docker security options? We are planning to use TigerBeetle and designed our whole application architect accordingly.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...