Skip to content
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

Closed
javijuji opened this issue Mar 28, 2023 · 5 comments
Closed

[Other] error bind mount using example compose file #35

javijuji opened this issue Mar 28, 2023 · 5 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@javijuji
Copy link

javijuji commented Mar 28, 2023

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

volumes:
  - ./config:/config

I tried changing this to

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

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

image
image

currently compose file without the sensitive info

`version: '3'
services:
romm:
image: 'zurdi15/romm:latest'
container_name: romm
network_mode: bridge0
environment:
- ROMM_DB_DRIVER="mariadb" # This variable can be set as: mariadb | sqlite. If it is not defined, sqlite will be the database by default
- DB_HOST=romm_db # Only if ROMM_DB_DRIVER='mariadb'
- DB_PORT=3306 # Only if ROMM_DB_DRIVER='mariadb'
- DB_USER=romm-user # Only if ROMM_DB_DRIVER='mariadb'
- DB_PASSWD=alreadychangedthis # Only if ROMM_DB_DRIVER='mariadb'
- CLIENT_ID=gottheclientid
- CLIENT_SECRET=gotthesecretaswell
- STEAMGRIDDB_API_KEY=WIP
volumes:
- ./volume1/data/media/roms:/library
ports:
- '82:80' #80 was in use by pihole. Changed this to 82 on host
depends_on:
- romm_db
restart: "unless-stopped"

romm_db:
image: lscr.io/linuxserver/mariadb:latest
container_name: romm_db
environment:
- MYSQL_ROOT_PASSWORD=changedthisone
- MYSQL_DATABASE=romm
- MYSQL_USER=romm-user
- MYSQL_PASSWORD=alsochangedthisone
volumes:
- ./config:/config #did not change this bind
ports:
- 3306:3306
restart: "unless-stopped"
`

@zurdi15 zurdi15 assigned zurdi15 and javijuji and unassigned zurdi15 Mar 28, 2023
@zurdi15 zurdi15 added the help wanted Extra attention is needed label Mar 28, 2023
@zurdi15 zurdi15 changed the title error bind mount using example compose file [Other] error bind mount using example compose file Mar 28, 2023
@ceratic
Copy link

ceratic commented Mar 28, 2023

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

@javijuji
Copy link
Author

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.

@javijuji
Copy link
Author

javijuji commented Mar 28, 2023

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

@javijuji
Copy link
Author

javijuji commented Mar 29, 2023

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?

@javijuji
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants