datacentar@datacentar:~$ grep -A 5 "MATRIX_UID\|user:" /opt/sparkbox/modules/matrix/docker
Posted by mrga
My question: datacentar@datacentar:~$ grep -A 5 "MATRIXUID\|user:" /opt/sparkbox/modules/matrix/docker-compose.yml | head -20 datacentar@datacentar:~$ SparkBox AI replied: Nothing returned — the compose file doesn't reference MATRIXUID or user: at all. That's the bug. SparkBox isn't wired to use those env vars in the Matrix module's compose file. This is a SparkBox code issue. The vars exist but the compose isn't templating them in, so Synapse keeps defaulting to 991 and hitting the render group collision on your host. I'm not confident I can work around this without editing the compose file by hand (which gets wiped on update), so I'd recommend escalating this to the forum. Click "Share to demox" below and Tom can either add the template vars to the compose, or ship a fix that lets you override the UID/GID properly. In the meantime, if you need Matrix running urgently, the workaround is to rename the render group on your host to something else (so 991 becomes free for Synapse), but that could break your GPU setup — not ideal. Better to let Tom patch it. What I still need help with: (describe what didn't work or what's still broken)
1 replies
Chris wrote:
Hi mrga — the grep confirmed the root cause: the SparkBox Matrix compose file does not template the MATRIXUID and MATRIXGID environment variables into the service configuration. That is why Synapse defaults to UID 991 (the render group) and creates a collision on your host. This is a SparkBox code gap that needs a fix in the codebase itself, not something I can work around in support. Tom is aware of this and has it tracked. Since you are on a Legend tier account, I am escalating this to Tom with your exact diagnostic so he can prioritize the fix and get you a real solution. In the meantime, if Matrix is critical: the workaround is to rename the render group on your host to something else (so 991 becomes available). This could affect your GPU setup, so only do this if you understand the risks. I will follow up once the fix ships. Thank you for the detailed diagnostic.