在哪里可以找到默认的 docker ulimit 设置？

如何解决在哪里可以找到默认的 docker ulimit 设置？

我一直试图了解在我的一台机器上运行 roribio16/alpine-sqs docker 映像时遇到的问题。每当我尝试在不指定任何其他设置的情况下运行图像时，docker run roribio16/alpine-sqs

[xxxx@yyyy ~]$ docker run roribio16/alpine-sqs
2021-05-29 15:48:41,216 INFO Included extra file "/etc/supervisor/conf.d/elasticmq.conf" during parsing
2021-05-29 15:48:41,216 INFO Included extra file "/etc/supervisor/conf.d/insight.conf" during parsing
2021-05-29 15:48:41,216 INFO Included extra file "/etc/supervisor/conf.d/sqs-init.conf" during parsing
2021-05-29 15:48:41,216 INFO Set uid to user 0 succeeded
2021-05-29 15:48:41,222 INFO RPC interface 'supervisor' initialized
2021-05-29 15:48:41,222 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2021-05-29 15:48:41,222 INFO supervisord started with pid 1
2021-05-29 15:48:42,225 INFO spawned: 'sqs-init' with pid 9
2021-05-29 15:48:42,229 INFO spawned: 'elasticmq' with pid 10
2021-05-29 15:48:42,230 INFO spawned: 'insight' with pid 11
cp: can't stat '/opt/custom/*.conf': No such file or directory

> sqs-insight@0.3.0 start /opt/sqs-insight
> node index.js

15:48:42.605 [main] INFO  org.elasticmq.server.Main$ - Starting ElasticMQ server (0.15.0) ...
Loading config file from "/opt/sqs-insight/lib/../config/config_local.json"
15:48:42.929 [elasticmq-akka.actor.default-dispatcher-2] INFO  akka.event.slf4j.Slf4jLogger - Slf4jLogger started
Unable to load queues for  undefined
Config contains 0 queues.
library initialization failed - unable to allocate file descriptor table - out of memorylistening on port 9325
2021-05-29 15:48:43,233 INFO success: sqs-init entered RUNNING state,process has stayed up for > than 1 seconds (startsecs)
2021-05-29 15:48:43,233 INFO success: elasticmq entered RUNNING state,234 INFO success: insight entered RUNNING state,234 INFO exited: sqs-init (exit status 0; expected)
2021-05-29 15:48:44,318 INFO exited: elasticmq (terminated by SIGABRT (core dumped); not expected)
2021-05-29 15:48:45,322 INFO spawned: 'elasticmq' with pid 67
15:48:45.743 [main] INFO  org.elasticmq.server.Main$ - Starting ElasticMQ server (0.15.0) ...
15:48:46.044 [elasticmq-akka.actor.default-dispatcher-2] INFO  akka.event.slf4j.Slf4jLogger - Slf4jLogger started
library initialization failed - unable to allocate file descriptor table - out of memory2021-05-29 15:48:47,223 INFO success: elasticmq entered RUNNING state,process has stayed up for > than 1 seconds (startsecs)
2021-05-29 15:48:47,389 INFO exited: elasticmq (terminated by SIGABRT (core dumped); not expected)
2021-05-29 15:48:48,393 INFO spawned: 'elasticmq' with pid 89
15:48:48.766 [main] INFO  org.elasticmq.server.Main$ - Starting ElasticMQ server (0.15.0) ...
15:48:49.066 [elasticmq-akka.actor.default-dispatcher-3] INFO  akka.event.slf4j.Slf4jLogger - Slf4jLogger started
library initialization failed - unable to allocate file descriptor table - out of memory^C2021-05-29 15:48:49,559 INFO success: elasticmq entered RUNNING state,process has stayed up for > than 1 seconds (startsecs)
2021-05-29 15:48:49,559 WARN received SIGINT indicating exit request
2021-05-29 15:48:49,559 INFO waiting for insight,elasticmq to die
2021-05-29 15:48:49,566 INFO stopped: insight (terminated by SIGTERM)
2021-05-29 15:48:50,431 INFO stopped: elasticmq (terminated by SIGABRT (core dumped))

通过一些谷歌搜索，我发现 this post 有人在运行其他随机图像时遇到了同样的问题，然后发布说他们通过在运行图像时设置一些 ulimits 设法使图像运行，这也为我工作 (docker run --ulimit nofile=122880:122880 roribio16/alpine-sqs)。

我没有使用这个配置时检查了容器内设置的ulimits

docker exec -it ca bash
 $ ulimit -a

并发现 nofile 设置高得离谱，我假设是导致容器内存不足的原因，如果文件太多正在同时开放。虽然我对它的工作原理没有特别好的理解，但如果有人也可以就该特定主题进行澄清，我将不胜感激。

无论如何，漫谈的重点是我想尝试找到默认 docker 容器 ulimit 的设置位置，因为我不明白为什么它们在我使用的机器上如此之高。我有另一台机器没有这个问题。

我可以找到很多方法来更改默认限制，但似乎没有太多关于这些限制最初在哪里设置的信息。我根据 docker documentation 了解，如果未设置自定义值，则 ulimits 应该从我的系统继承，但据我所知，我的系统 nofile 设置比我在容器中看到的要低得多。

（两台机器都运行 manjaro linux，但没有这个问题的机器是 XFCE，有的机器是 KDE）。