-
Notifications
You must be signed in to change notification settings - Fork 2
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
First-time setup: installation issues #42
Comments
Dear @Johnnywang92 , I believe you have not configured the <absolute path > in the docker-compose.yml file. |
Dear @Johnnywang92 , The device folders are incorrectly specified in your docker-compose.yml, please remove the '<' and '>'.
|
Thank you so much Laurens van de Wiel, it worked.
Is that means I need create a user "metadom_user" in mysql? |
Dear @Johnnywang92 Is the first command you executed the one specified at https://github.com/cmbi/metadome/blob/master/README.md#first-time-set-up ? If not, please tear down the existing architecture via the command |
Dear @laurensvdwiel |
@cbaakman , could you attempt to replicate this issue? |
When I run this on my desktop:
I get the following output:
|
It looks like "db.create_all" is called twice. Once in the app creation and once in the install procedure. |
@cbaakman : is this issue resolved? |
Unfortunately not, it's still happening! |
Duplicate issue at #69 Am looking into this from my end the coming weeks |
when I run the install command on MAC Mojave (Python 2.7.10), get error message as following:
Starting metadome_redis_1 ... done
Starting metadome_rabbitmq_1 ... done
Creating metadome_db_1 ... error
ERROR: for metadome_db_1 Cannot create container for service db: b"error while mounting volume with options: type='none' device='' o='bind': no such file or directory"
ERROR: for db Cannot create container for service db: b"error while mounting volume with options: type='none' device='' o='bind': no such file or directory"
ERROR: Encountered errors while bringing up the project.
Any suggestion?
The text was updated successfully, but these errors were encountered: