-
-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Other] error bind mount using example compose file #35
Comments
Try leaving the leading "." within the volume mapping.
instead of
That should fix your problem when mounting the dir within DSM7 |
Done! Thank you. Working now. |
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: tried deploying on docker synology and docker baremetal on a NUC with same results |
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) 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? |
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. |
I tried running the example compose file and keep getting an error related to a missing bind mount.
failed to deploy a stack: time="2023-03-28T13:30:15Z" level=warning msg="The "Vi" variable is not set. Defaulting to a blank string." Network romm_default Creating Network romm_default Created Container romm_db Creating Container romm_db Created Container romm Creating Container romm Created Container romm_db Starting Error response from daemon: Bind mount failed: '/data/compose/56/config' does not exists
I am guessing this is related to the following:
Also not sure what the undefined Vi variable is
I tried changing this to
failed to deploy a stack: time="2023-03-28T13:34:24Z" level=warning msg="The "Vi" variable is not set. Defaulting to a blank string." Network romm_default Creating Network romm_default Created Container romm_db Creating Container romm_db Created Container romm Creating Container romm Created Container romm_db Starting Error response from daemon: Bind mount failed: '/data/compose/58/volume1/docker/romm' does not exists
Should I create a config folder inside the data folder? I'd rather have config files in volume1/docker/romm and roms in volume1/data/media/roms
I can see it did actually try to create the database
currently compose file without the sensitive info
The text was updated successfully, but these errors were encountered: