Installation help for Synology

[Zaldans]

Super new to docker and wanted to check out yuvomi, but I'm running into issues installing it on my Synology NAS.

after following the docker installation instructions I get this error during the build "Validating /volume1/docker/yuvomi/docker-compose.yml: services.yuvomi.env_file.0 must be a string"

I am able to get rid of this error and get a successful build by tweaking the docker-compose.yml file:
line 27 env_file: - path: .env required: false to env_file: - .env

But then it fails and stops instantly.

I'm running DSM 7.3.2-86009 Update 4 and Docker Version 24.0.2 API version: 1.43

Any help would be greatly appreciated and thanks in advanced!

[ulsklyc]

Not user error - this one is on us, and your workaround is exactly the right fix.

docker-compose.yml passes the .env in Compose's long form:

env_file:
  - path: .env
    required: false

That syntax only exists from Compose v2.24 (January 2024) onwards. Anything older rejects the whole manifest rather than just that field, which is why you get services.yuvomi.env_file.0 must be a string before anything even tries to start. DSM ships a Compose plugin predating it, so every Synology install hits this. Same for QNAP and older distro packages.

The long form was added for Git/GitOps stacks that clone the repository without a .env (#698). That path has had its own file since - docs/docker-compose.portainer.yml - so the long form was buying nothing and breaking every older engine. It is back to the short form - .env on main, which is what podman-compose.yml has used all along, plus a test so it cannot drift back. It goes out with the next release.

Until then your edit is the fix - keep it.

The second failure

That one I cannot diagnose from here, so two questions:

1. What do the logs say?

docker compose logs yuvomi | tail -30

The most likely answer is that the .env exists but has no SESSION_SECRET. The app refuses to start without it and exits immediately, which matches "fails and stops instantly". Two values are mandatory:

SESSION_SECRET=<random, min 32 chars>
DB_ENCRYPTION_KEY=<random, min 32 chars>

Generate them with openssl rand -hex 32. DB_ENCRYPTION_KEY cannot be changed later on an existing database, so back it up.

2. Are you building from source?

You mentioned "during the build". If you are running --build, you do not need to - the standard path pulls a pre-built image and skips compiling the native database module on the NAS entirely:

docker compose pull && docker compose up -d

If the logs show a permissions error on /data instead, that is a different and also very Synology-specific one - post it and we will take it from there.

Thanks for the report, and for narrowing it down to the exact line before posting. That is what made it a five-minute diagnosis.

[ulsklyc]

Fixed in v2.13.0, released a moment ago. docker-compose.yml is back on the short env_file form, so it parses on Synology DSM and every other engine with a Compose older than v2.24. A test now holds that across all Compose manifests in the repository so it cannot drift back.

Pull the new file and you can drop your local edit:

curl -O https://raw.githubusercontent.com/ulsklyc/yuvomi/main/docker-compose.yml
docker compose pull && docker compose up -d

If the second failure is still there after that, open a new discussion with the output of docker compose logs yuvomi | tail -30 and we will take it from there. Thanks for isolating it to the exact line - that is what made it a five-minute diagnosis.