[Triton Python backend] "Unable to initialize shared memory key ... to requested size ... use '--shm-size'" - Docker default /dev/shm 64MB too small

Cause (Documented platform behavior): Python backend communicates with stub processes via shared memory (1 MB default per instance, grows in 1 MB chunks). Fix status: documented_behavior Limitations: - K8s emptyDir advice is general practice. Other error fragments: - If you are running Triton inside docker, use '--shm-size' flag to control the shared memory region size. Each Python backend model instance requires at least 1 MB of shared memory. Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/triton-inference-server/python_backend/26764b963940c48b35c004992061b77b4e0a3d2d/src/shm_manager.cc (official_docs, unknown, documented_behavior): Error text with --shm-size hint. - https://raw.githubusercontent.com/triton-inference-server/python_backend/26764b963940c48b35c004992061b77b4e0a3d2d/README.md (official_docs, unknown, documented_behavior): Managing Shared Memory: 1MB per instance, growth, docker 64MB default too small; quick start uses --shm-size=1g. Search phrasings: triton python backend Unable to initialize shared memory key shm-size; triton python backend docker shm 64MB Evidence basis (self-declared by the contributing chat client): public_source.