Replies: 1 comment
-
|
Please update to 0.11.3, I believe it is fixed there. ramalama info now shows config file parsing. And will read all of the config files. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Ramalama appears to be ignoring the configuration file located at $HOME/.config/ramalama/ramalama.conf despite the file being present and containing valid configuration options. But if i run it with
RAMALAMA_CONFIG="$HOME/.config/ramalama/ramalama.conf" ramalama run graniteit works.Environment Details
Ramalama Info;
From inside the container!:
Not mounting $HOME/.config/ramalama/ramalama.conf !?
Configuration File Details
File Location and Permissions
Current Configuration Settings
The configuration file exists at the expected location ($HOME/.config/ramalama/ramalama.conf) and contains several customized settings:
According to the documentation in the config file, ramalama should read configuration files in this order:
/usr/share/ramalama/ramalama.conf
/etc/ramalama/ramalama.conf
$XDG_CONFIG_HOME/ramalama/ramalama.conf or $HOME/.config/ramalama/ramalama.conf
Expected vs Actual Behavior
Expected Behavior
Ramalama should read and apply the configuration from $HOME/.config/ramalama/ramalama.conf, using the custom values like ngl = 27 and transport = "huggingface".
Actual Behavior
When running ramalama with debug output, there’s no indication that the configuration file is being read or processed. The behavior suggests default values are being used instead of the configured ones.
Steps to Reproduce
Debug Output Sample
When running ramalama --debug run model, the debug output shows system detection and container operations but no evidence of configuration file parsing:
Additional Information
File permissions appear correct (readable by user)
Directory structure matches expected layout
XDG_CONFIG_HOME is properly set
No apparent syntax errors in the TOML configuration
Check SElinux, didnt notice anything myself. But its still selinux...
Has anyone else experienced this issue? Are there any known workarounds or troubleshooting steps that might help identify why the configuration file is being ignored?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions