Describe the bug
When ulimit -a is performed in regular machine' shell we got:

POSIX message queues (bytes, -q) 4194304

But Github runners are limiting it to another value. If we run the same command in runner shell:

POSIX message queues (bytes, -q) 819200

The runner is installed in the same machine, although it cannot use the same resource as set.

In our /etc/security/limits.conf we have:

* hard msgqueue 4194304
<$USER> hard msgqueue 4194304
root hard msgqueue 4194304
* soft msgqueue 4194304
<$USER> soft msgqueue 4194304
root soft msgqueue 4194304

How can Github self-hosted runner access the same amount of memory?

To Reproduce
Just run ulimit -a in Github runner shell, if you have changed the default value for the desired ulimit.

Expected behavior
When we run ulimit -a we should see POSIX message queues (bytes, -q) 4194304

Actual behavior
When we run ulimit -a we see POSIX message queues (bytes, -q) 819200

Runner Version and Platform

Version of your runner? Current runner version: '2.317.0'

OS of the machine running the runner? Ubuntu 22.04

What's not working?

> Run ulimit -q 4194304
ulimit -q 4194304 
Error: Process completed with exit code 1.