I added a task for systemd to consider raising the default RLIMIT_MEMLOCK limit.
This upstream commit raises the default limit to 8Mb: https://github.com/systemd/systemd/commit/852b62507b2 The way things are now, the following scenario does NOT work out of the box: - jammy lxd on focal host - apt install mariadb-server mariadb will crash and core dump because of the low MEMLOCK limit. Its systemd service file even has this line to raise the limit: LimitMEMLOCK=524288 But that does not have any effect from inside the unprivileged lxd container. Jammy lxd on jammy host will work just because the jammy kernel (5.15.0) is deemed unsafe[1] for uring by mariadb, and then uring is disabled during startup. 1. https://github.com/MariaDB/server/blob/10.6/storage/innobase/handler/ha_innodb.cc#L19480 ** Summary changed: - FTBFS: test failure due to low memlock limit + FTBFS: mariadb fails to start due to low MEMLOCK limit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970634 Title: FTBFS: mariadb fails to start due to low MEMLOCK limit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
