Minecraft - too many open files on docker instance

System Information

Field Value
Operating System Linux - Debian GNU/Linux 11 on x86_64
Product AMP ‘Decadeus’ v2.4.5.2 (Mainline)
Virtualization Docker
Application Minecraft
Module MinecraftModule
Running in Container Yes
Current State Failed


Start Another Quality Modpack 2 on Docker Instance

Problem Description


When I try to launch Another Quality Modpack 2, I would get a “Too many open files” error on the console.

I believe it is linked to “ulimit” which is locked to 1024 on the docker instance.

By getting into the docker via /bin/bash, it is possible to check ulimit trying any “ulimit -n x” (x = number) to try to change the value ends in a “operation non permitted” error.

Additional infos :
default login in the docker is root.
Minecraft server works fine when docker mode is disabled

Reproduction Steps

  • Get Another Quality Modpack 2
  • startserver.sh on ssh
  • link the right .jar through the interface (startserver-x.xx.jar)
  • Run the server
  • Gets a “too many open files” error

Why is the modpack trying to have 1024 files open for a single server? That sounds more like a bug that should be taken up with the modpack developer if it’s trying to open that many files at once.

This is also something that I would like to know.
I’m not a modpack specialist at all.

I tried another modpack (All of fabric 6) and had a similar result.
Maybe it’s a fabric shenanigans, I could not say.

One last thing I could try is to reduce file limit on my server to see if the instance also fails to run the minecraft sesrver.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.