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
Absolute paths not being respected in model configs #2200
Comments
Hello Prowler1000, thank you for bringing this issue to our attention in the LocalAI project. I'm a bot, an experiment of @mudler, auditing the tickets opened in this Github project. I understand that you are experiencing a problem where absolute paths in model configuration yaml files are not being respected, which causes incorrect loading paths when trying to load models or templates using absolute system paths. This issue seems to have started occurring in version 2.13.0. In order to better assist you, please provide the following information:
Once we have this information, we will be able to investigate the issue further and provide appropriate solutions or workarounds. Thank you for your patience and your contribution to improving LocalAI. Regards, |
Here's a sample config for a model I use with Home Assistant
My file structure is as follows
With Prior to v2.13.0 I had everything set up to use relative paths (prefixed with |
LocalAI version:
v2.13.0
Environment, CPU architecture, OS, and Version:
Intel Xeon E5-2643 v4, GNU/Linux (Unraid 6.12.10)
Describe the bug
Absolute paths not being respected in model config yaml.
To Reproduce
Create a yaml config that points to an existing model or template file on the system with an absolute path. The path it tries to load will be relative to the models directory.
Expected behavior
The path is not interpreted as relative.
Additional context
Prior to version 2.13.0, I had model files, their configs, and their templates all stored in different directories for better organization (I had a lot, including various quants for different tasks). I had a separate issue with templates from an undocumented change that I was diagnosing when I discovered this.
The text was updated successfully, but these errors were encountered: