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

Error in first step during docker-compose #40

Closed
parwinderau opened this issue Apr 10, 2024 · 3 comments
Closed

Error in first step during docker-compose #40

parwinderau opened this issue Apr 10, 2024 · 3 comments

Comments

@parwinderau
Copy link

I am trying to test the true connector.
I followed the steps given in the 1st video.
However, after cloning the repo when I try to shoot the docker compose up command it gives the below error:

✔ Network trueconnector_provider Created 0.0s
✔ Network trueconnector_consumer Created 0.0s
✔ Volume "trueconnector_uc_provider_data" Created 0.0s
external volume "trueconnector_be_dataapp_provider_data" not found

when I saw the docker-compose.yml file I can see "external" field is set to "true" by default under "trueconnector_be_dataapp_provider_data" block. If I change it "false", the installation move forward but not sure if it has any impact on further operations.
Please fix this issue.

Thanks
Parwinder Singh (PhD researcher)
BTECH, Aarhus University, Denmark

@davidjovanovic
Copy link
Collaborator

Hello Parwinder,

Were happy that someone new is trying out our TRUE Connector!
Regarding the issue, it actually works as intended, you need to setup an external volume as explained here.
The videos are a bit outdated, you can still use them for a general know how if you never used Postman, Docker etc. For a more detailed and correct explanation of the setup please follow our written documentation.

Thank for your help and for using the TRUE Connector!
David Jovanovic

@parwinderau
Copy link
Author

parwinderau commented Apr 10, 2024 via email

@parwinderau
Copy link
Author

I have figured it out what is the problem. I was giving a path in incorrect way. I was using windows docker and C:/; so the problem was with the semicolon. When I simple use "/" in place of ":" it started working. For example ; /c/my/path/to/folder/ is a valid way. But still there were some issues with docker volumes on windows environment. So I switched it to the linux ubuntu 20.04 (under Azure VM) and its installation is working fine there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants