Unable to install on my Ubuntu 26.04

[fever7-beep]

Hello everyone,
I can't get DreamServer to install on my PC.
Here is the error message from the log file:

_dreamserver [ERROR]^[[0m Type validation errors:

• COMFYUI_CPU_LIMIT: expected number, got '16,0' (line 88)
• COMFYUI_CPU_RESERVATION: expected number, got '16,0' (line 89)
• HERMES_CPU_LIMIT: expected number, got '4,0' (line 86)
• HERMES_CPU_RESERVATION: expected number, got '0,5' (line 87)
• TTS_CPU_LIMIT: expected number, got '8,0' (line 82)
• TTS_CPU_RESERVATION: expected number, got '2,0' (line 83)
• WHISPER_CPU_LIMIT: expected number, got '4,0' (line 84)
• WHISPER_CPU_RESERVATION: expected number, got '1,0' (line 85)_

I have a Ryzen 5700X, 32 GB of DDR4 RAM, and an RTX 5060 Ti with 16 GB of VRAM.

Thank you in advance, and have a great day.

Best regards,

[cookesan]

The immediate blocker is the decimal separator in .env.

Those CPU values are schema number values, and the validator only accepts digits with an optional dot decimal part. So values like 16,0, 4,0, and 0,5 fail exactly as shown. Use 16.0, 4.0, and 0.5 instead.

For the values in your log, the minimal edit is:

COMFYUI_CPU_LIMIT=16.0
COMFYUI_CPU_RESERVATION=16.0
HERMES_CPU_LIMIT=4.0
HERMES_CPU_RESERVATION=4.0
TTS_CPU_LIMIT=8.0
TTS_CPU_RESERVATION=2.0
WHISPER_CPU_LIMIT=4.0
WHISPER_CPU_RESERVATION=1.0

The installer code normally writes dot-decimal values such as 8.0, 4.0, 2.0, 1.0, and 0.5, and Docker Compose consumes those values as cpus: limits/reservations. So this does not look like an Ubuntu 26.04 or GPU problem; it looks like locale-style comma decimals ended up in the generated or edited .env.

After changing the commas to dots, rerun the installer. If you want to check just the environment file first, run the project's env validation script again and the type errors for those lines should disappear.

[fever7-beep]

Thanks for your feedback.
I added the new settings to the .env file by replacing the old ones.
When I restart the installation, I get this error message:

[ERROR] Generated .env failed schema validation. See /tmp/dream-server-install.log for details.

Sorry, that's an area I'm not familiar with.
And when I go back to the .env file, I see that the incorrect settings have reappeared.
What should I do, please?

[cookesan]

That makes sense: the installer regenerates .env during phase 06, so editing the generated file can be overwritten on the next run.

The important clue is still in /tmp/dream-server-install.log. If the new log again lists the CPU values with commas, this is probably coming from the system locale while the installer formats those auto CPU budgets. The generator uses numeric formatting for values like 16.0 and the schema validator only accepts dot-decimal numbers, so a locale that formats decimals as 16,0 can recreate the same invalid values.

Try rerunning the installer with a C numeric locale:

LC_ALL=C ./install.sh

or, if you are launching it from inside the dream-server directory:

LC_ALL=C bash ./install.sh

Before rerunning, it is fine to remove the failed generated .env in the install directory, but the main fix is the locale on the installer process, not another manual edit after generation.

If it still fails, paste just the Type validation errors: block from /tmp/dream-server-install.log. That block should show the exact key names and line numbers without needing to share the whole log.

[fever7-beep]

Hello,

Thank you. It works.

Yes, I'm French. So my Ubuntu is in French.

Thanks again, and have a great day.

Best regards,