failed starting, not enough memory (docker)

[someson]

Describe the bug

2024-04-17 10:18:46 I20240417 08:18:46.687839     1 init.cc:70] dragonfly running in opt mode.
2024-04-17 10:18:46 I20240417 08:18:46.688548     1 dfly_main.cc:627] Starting dragonfly df-v1.15.0-0c1150956b600f21473eae1d0e338194de6b61bc
2024-04-17 10:18:46 W20240417 08:18:46.688669     1 dfly_main.cc:666] SWAP is enabled. Consider disabling it when running Dragonfly.
2024-04-17 10:18:46 I20240417 08:18:46.688719     1 dfly_main.cc:671] maxmemory has not been specified. Deciding myself....
2024-04-17 10:18:46 I20240417 08:18:46.688724     1 dfly_main.cc:680] Found 1.50GiB available memory. Setting maxmemory to 1.20GiB
2024-04-17 10:18:46 I20240417 08:18:46.689167     8 uring_proactor.cc:172] IORing with 1024 entries, allocated 102464 bytes, cq_entries is 2048
2024-04-17 10:18:46 I20240417 08:18:46.690090     1 proactor_pool.cc:146] Running 10 io threads
2024-04-17 10:18:46 E20240417 08:18:46.690114     1 dfly_main.cc:157] There are 10 threads, so 2.50GiB are required. Exiting...

To Reproduce
Steps to reproduce the behavior:
docker-compose.yml:

    service-dragonfly:
        image: 'docker.dragonflydb.io/dragonflydb/dragonfly'
        container_name: service-dragonfly
        ulimits:
            memlock: -1
        command: dragonfly --requirepass "${REDIS_PASSWORD}" --admin_nopass --cache_mode
        ports:
            - "6379:6379"
        restart: unless-stopped
        volumes:
            - .docker/dragonfly/data:/data

docker-compose up -d --build

Expected behavior
dragonfly is up and running

Environment (please complete the following information):

• OS: Apple M1 Max [Sonoma 14.4.1]
• Kernel: Darwin MacBook-Pro-user.local 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000 arm64
• Containerized: [Docker Compose]
• Dragonfly Version: [last one]

[romange]

please add --proactor_threads=4 argument to limit it running on 4 threads

[someson]

why then with Deciding myself.... couldn't reduce amount of threads also?
Please, consider updating documentation for this particular case

[romange]

Not a bad idea about extending the heuristic to threads as well. Regarding the documentation - there is "edit this page" link at the bottom. Feel free to send a PR if something was not clear 🙇🏼‍♂️