-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Kafka failed to run #13
Comments
Seems like it is related to usage of {HOME} in "volume" field for many services docker-compose file.
|
Thanks for raising this issue @vpankaj97! Initially, I thought of persisting data for services outside of the repo but was under the assumption that it would have write permissions. I think it is a good idea to persist it in a relative pathway given it should have write access but to persist in a specific folder pattern that all services follow. This will help try to keep the |
Makes sense. Currently, I just made: Though, I'm still facing issues, ex - MYSQL not working, Cassandra not working, Kafka broker not found. |
|
Thanks for reporting this problem as well. Looks like in version 8.4.0 of MySQL, we need to use the command |
I tried in my laptop by changing to use |
I ran into this issue recently when running on GitHub Actions and it's due to the user on the host being different to the user in the container. I have now changed the default behaviour of insta-infra to not persist data so it should work without having to worry about folder permissions. To persist data, you now need to include the flag I will close this issue now. |
System - Windows 11
Docker on WSL2
Note. Inititated from inside WSL2 Ubuntu instance
Log:
The text was updated successfully, but these errors were encountered: