[Other] error bind mount using example compose file about romm HOT 5 CLOSED

Try leaving the leading "." within the volume mapping.

volumes:
  - /volume1/docker/romm:/config

instead of

volumes:
  - ./volume1/docker/romm:/config

That should fix your problem when mounting the dir within DSM7

from romm.

Try leaving the leading "." within the volume mapping.

volumes:
  - /volume1/docker/romm:/config

instead of

volumes:
  - ./volume1/docker/romm:/config

That should fix your problem when mounting the dir within DSM7

Done! Thank you. Working now.

from romm.

Getting a different error now but it is unrelated. Containers get created but library scan shows

Couldn't complete scan. Something went wrong...

romm log shows:
CRITICAL: [ROMM] Not supported "mariadb" database

tried deploying on docker synology and docker baremetal on a NUC with same results

from romm.

Apparently using @ and such in the db credentials messes things up. Changed it to letters and numbers only and got past that error. Latest error in romm log is:

2023-03-29T01:13:57.943530855Z sqlalchemy.exc.OperationalError: (mariadb.OperationalError) Access denied for user 'romm-user'@'romm.bridge0' (using password: YES)
2023-03-29T01:13:57.943572117Z (Background on this error at: https://sqlalche.me/e/20/e3q8)

Still getting Couldn't complete scan. Something went wrong... but at least the app deployed.

Anyone got a working compose file for docker running on synology?

from romm.

Managed to get this working. Forgot to delete the old database after redeploying the new stack which means database was using the old (Invalid because it had @) DB password.

from romm.