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

Updated readme.md to contain troubleshooting section with issue I had #195

Merged
merged 1 commit into from
Apr 27, 2023

Conversation

decoles
Copy link
Contributor

@decoles decoles commented Apr 25, 2023

I was having issues getting my docker-compose to install new packages when cloning to a new device. And this change fixed my issues, figured others may have this problem.

Copy link
Contributor

@hardikpatil hardikpatil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just tested it, seems to working but not sure what the difference is that fixed it @decoles @briswells , this one combines both building and starting containers into one command

before:
Screenshot 2023-04-27 at 10 18 05

After:
Screenshot 2023-04-27 at 10 24 36

@briswells
Copy link
Contributor

That is correct. I thought I updated to README to reflect this but I guess not. Whenever a new library is added the containers need to be rebuilt. After the container has been built once though you can use docker compose to run them without the build flag. Nice call out!

@hardikpatil hardikpatil merged commit bd52c67 into main Apr 27, 2023
@hardikpatil hardikpatil deleted the update_readme_troubleshooting branch April 27, 2023 22:10
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

Successfully merging this pull request may close these issues.

3 participants