Skip to content
This repository was archived by the owner on Jan 12, 2026. It is now read-only.
This repository was archived by the owner on Jan 12, 2026. It is now read-only.

Inconsistency between "Starting Ray with <x> GiB" and docker shm_size: <y> #185

Description

@free-soellingeraj

My docker-compose.yml defines the shm_size: '32gb' but when I run ray.init(num_cpus=4, ignore_reinit_error=True, include_dashboard=False) I get the log line:

2020-08-26 20:31:09,651 INFO resource_spec.py:231 -- Starting Ray with 37.5 GiB memory available for workers and up to 18.76 GiB for objects. You can adjust these settings with ray.init(memory=<bytes>, object_store_memory=<bytes>).

So I am naturally curious:

How is ray getting more memory than is allotted to the container in which it's running?

Thanks in advance

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions