Installation/Startup issues on NixOS: ModuleNotFoundError and group render Docker errors

baksteendebrik commented

2026-06-01 14:57:10 +02:00

(Migrated from github.com)

Description:
Running Odysseus on NixOS (using the provided Docker Compose and native setup attempts) leads to two main issues:

Native setup: Fails to build or import Python C-extensions (like numpy) due to missing libstdc++.so.6 in the standard path, which is a common occurrence on NixOS due to the non-FHS filesystem.

Docker setup: Fails with Error response from daemon: Unable to find group render when attempting to use the GPU via the gpu.amd.yml overlay. This appears to be because the NixOS render group is not mapped or available inside the python:3.12-slim container.

Steps to reproduce:

Clone the repository on a NixOS system.

Attempt to run docker compose up -d with gpu.amd.yml enabled.

Observe error: Unable to find group render: no matching entries in group file.

Environment:

OS: NixOS 26.05

Docker: Rootless mode

GPU: AMD RX 9070 XT (ROCm drivers on host)

I am a computer science student and have been daily driving on NixOS for 2 years. If you will allow it i'd like to fix the compatibility issues for NixOS systems. I could add nix flake files or change the docker configs themselves. Although it would probably be better to make the nix flake files.

Let me know your thoughts!

I am excited to help make this project compatible on as much devices as possible and try to improve it as much as possible.

Description: Running Odysseus on NixOS (using the provided Docker Compose and native setup attempts) leads to two main issues: Native setup: Fails to build or import Python C-extensions (like numpy) due to missing libstdc++.so.6 in the standard path, which is a common occurrence on NixOS due to the non-FHS filesystem. Docker setup: Fails with Error response from daemon: Unable to find group render when attempting to use the GPU via the gpu.amd.yml overlay. This appears to be because the NixOS render group is not mapped or available inside the python:3.12-slim container. Steps to reproduce: Clone the repository on a NixOS system. Attempt to run docker compose up -d with gpu.amd.yml enabled. Observe error: Unable to find group render: no matching entries in group file. Environment: OS: NixOS 26.05 Docker: Rootless mode GPU: AMD RX 9070 XT (ROCm drivers on host) I am a computer science student and have been daily driving on NixOS for 2 years. If you will allow it i'd like to fix the compatibility issues for NixOS systems. I could add nix flake files or change the docker configs themselves. Although it would probably be better to make the nix flake files. Let me know your thoughts! I am excited to help make this project compatible on as much devices as possible and try to improve it as much as possible.

👍 1

baksteendebrik commented

2026-06-01 15:11:04 +02:00

(Migrated from github.com)

I also want to add this to the issue case on how I would proceed implememting the features:
My plan is to add a /nix directory to the repository containing a flake.nix and flake.lock. I believe this is the best path forward for a few reasons:

Reproducibility & Security: By using a flake.lock file, we ensure cryptographically verified, bit-for-bit identical environments for every user, which perfectly aligns with the project's 'local-first, privacy-first' philosophy.  

Platform Agnostic: While I am using NixOS, providing a Nix flake means this will work on any Linux distribution that has the Nix package manager installed, solving dependency hell across the board.  

Clean Decoupling: Keeping these files in a dedicated /nix directory ensures the core application logic and current Docker structure remain completely untouched and clean for existing users.

I’m happy to implement this as an optional enhancement so we can guarantee a solid native experience for power users while keeping the Docker workflow exactly as it is.

Does this align with your vision for the project's development environment?"

I also want to add this to the issue case on how I would proceed implememting the features: My plan is to add a /nix directory to the repository containing a flake.nix and flake.lock. I believe this is the best path forward for a few reasons: Reproducibility & Security: By using a flake.lock file, we ensure cryptographically verified, bit-for-bit identical environments for every user, which perfectly aligns with the project's 'local-first, privacy-first' philosophy. Platform Agnostic: While I am using NixOS, providing a Nix flake means this will work on any Linux distribution that has the Nix package manager installed, solving dependency hell across the board. Clean Decoupling: Keeping these files in a dedicated /nix directory ensures the core application logic and current Docker structure remain completely untouched and clean for existing users. I’m happy to implement this as an optional enhancement so we can guarantee a solid native experience for power users while keeping the Docker workflow exactly as it is. Does this align with your vision for the project's development environment?"

Dr-Shadow commented

2026-06-01 15:17:34 +02:00

(Migrated from github.com)

Have a look on #515 for a fix in the docker environment

HirschBerge commented

2026-06-01 15:27:00 +02:00

(Migrated from github.com)

Having this be native instead of a container for Nix installation would be great regardless
<3

Having this be native instead of a container for Nix installation would be great regardless <3

baksteendebrik commented

2026-06-01 15:30:51 +02:00

(Migrated from github.com)

okay first I will ensure that everything is tidy on my system for the nix package manager and then i'll create a PR cheers guys!

🎉 2

Gamermoments6793 commented

2026-06-01 16:34:09 +02:00

(Migrated from github.com)

working for 8 hours today :( but I would love to help test it out for you if needed!

baksteendebrik commented

2026-06-01 18:22:54 +02:00

(Migrated from github.com)

yeah for sure man! I'm trying to make it as streamlined as possible so everything will be automatically configured by running 1 or 2 commands!

❤️ 1

sleepy commented

2026-06-01 19:31:33 +02:00

Owner

||Closing — NixOS installation issues. Out of scope.

sleepy closed this issue

2026-06-01 19:31:33 +02:00

Rows
Columns

Installation/Startup issues on NixOS: ModuleNotFoundError and group render Docker errors #503