-
-
Notifications
You must be signed in to change notification settings - Fork 25
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 response from daemon: Unable to find group render: no matching entries in group file #101
Comments
Thank you for reporting this! I need more investigation into AMD Docker Support. Since I have not an AMD GPU, I need some time to get this sorted out or some help from the community to contribute. |
For now, you can remove the ollama service from the docker compose and point to a manually installed ollama instance on your system in the |
I'm working on trying to figure out how to do this. I do have ollama running locally (non-docker) so if I can it might work fine. I updated the .env file, that was easy, but modifying the docker-compose.base.yml is proving to be a challenge. I don't think I will be able to test AMD GPU ROCm support because my GPU is not actually supported yet. The AMD GPU that I have is the iGPU on the AMD Ryzen 7 7730U. |
You can try to just remove this line: https://github.com/TilmanGriesel/chipper/blob/main/docker/docker-compose.base.yml#L52 |
That produced a different error so I commented out line 51 and 52 and that didn't work. Then, I commented out line 47 and everything fired up fine. |
Thanks! I will try to add a flag to the |
Sorry got really busy. Thank you for the changes! I pulled the changes but I'm hesitant to run docker again because it messes up waydroid on my system and I haven't found a way to make them play nicely together yet (and waydroid running well is high priority for me atm). Chipper ran fine with the changes that I made and because I may not get to figuring out why docker and waydroid don't play nicely together I would like to close this issue and not leave it hanging open. Thanks again for the nifty app! |
The text was updated successfully, but these errors were encountered: