Any suggestion on how to increase permanently the

ulimit

with

WSL2

I can't make it work correctly on Windows, every time I get, I also tried to modify different files following many tutorial, I still have the warning at the beginning...

ulimit -n 65536
-bash: ulimit: open files: cannot modify limit: Operation not permitted

WSL2 is not specific enough, its really down to the Linux distribution you use. Which is that? And systemd or no? I think WSL2 supports systemd.

Ubuntu 22.04 LTS

Ok, just a sec.

so far tried the classic

ulimit

command like describe above, I have tried to add my user to

/etc/security/limits.conf

but without luck (still at 1024) and also tried

sudo prlimit -p "$$" --nofile=10000:10000
exec zsh
ulimit -n 10000

which work but only for the running session

I just added that new line at end of file:

$ whoami
jsirois
$ tail -5 /etc/security/limits.conf
#@student        -       maxlogins       4

# End of file

jsirois         hard    nofile           65536

Then over in powershell:

> wsl -t Ubuntu-22.04
The operation completed successfully.

Then opened a new Ubuntu-22.04 session:

$ ulimit -n
1024
$ ulimit -n 65536
$ ulimit -n
65536
$ ulimit -n 65537
-bash: ulimit: open files: cannot modify limit: Operation not permitted

@enough-analyst-54434 thanks now I can run correctly

ulimit -n 65536

but I still have this warning

11:44:23.78 [WARN] File handle limit is capped to: 4096. To avoid 'too many open file handle' errors, we recommend a limit of at least 10000: please see <https://www.pantsbuild.org/docs/troubleshooting#too-many-open-files-error> for more information.

when running Pants

And you

pkill pantsd

or however you ensure Pantsd is down and then re-started it afresh after you bumped to 65K?

@enough-analyst-54434 I realized I still can't exec

ulimit -n 65536

with my user (I was typing

ulimit 65536

without the

-n

) so no, even with the edit of my

/etc/security/limits.conf

I can't modify (restarted WSL, restarted my pc, wipe all pants cache just to be sure)

Huh, not sure what to say about that.

No stress, anyway it work in the pipeline correctly, that was just for local development and I understand the problem is not coming from Pants but from WSL and Windows...

Ok ~good, but even more mysterious then since you and I have the superficially same setup and I do not have your experience.

yup I am in adm

id
uid=1000(cerberus) gid=1000(cerberus) groups=1000(cerberus),4(adm),20(dialout),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),117(netdev),1001(docker)

Ok, no clue really.

nope pure bash

K, truly out of ideas then.

it works for the zsh session only doing it that way

Ok.

but no result for bash

which bash

? Because, very weird to me but:

jsirois@Gill-Windows:~/dev/pantsbuild/jsirois-scie-pants (one_step_setup/parity) $ which bash
/usr/bin/bash
jsirois@Gill-Windows:~/dev/pantsbuild/jsirois-scie-pants (one_step_setup/parity) $ /mnt/c/Program\ Files/Git/bin/bash.exe

John Sirois@Gill-Windows MINGW64 //wsl.localhost/Ubuntu-22.04/home/jsirois/dev/pantsbuild/jsirois-scie-pants
$

IOW the Git bash.exe Windows executable works under WSL. I don't really understand WSL. And Git bash fails:

John Sirois@Gill-Windows MINGW64 //wsl.localhost/Ubuntu-22.04/home/jsirois/dev/pantsbuild/jsirois-scie-pants
$ ulimit -n
3200

John Sirois@Gill-Windows MINGW64 //wsl.localhost/Ubuntu-22.04/home/jsirois/dev/pantsbuild/jsirois-scie-pants
$ ulimit -n 10000
bash: ulimit: open files: cannot modify limit: Too many open files

John Sirois@Gill-Windows MINGW64 //wsl.localhost/Ubuntu-22.04/home/jsirois/dev/pantsbuild/jsirois-scie-pants
$

launching Ubuntu with

ubuntu run bash

and I get

/usr/bin/bash

on the

which bash

Ok. That was the only way I could repro a ulimit set failure at any rate, using Windows bash.exe under WSL2 Ubuntu-22.04.