Hello,
The property config_path of lxc_container struct is described in documentation as: Full path to configuration file. Additionally, description of its get and set functions also confirm this statement (that it should resemble configuration file of a specific container).
Having this in mind, I would assume that I can use set_config_path to set this value to e.g. /home/lxc/testcontainer/config (my LXC directory is /home/lxc).
However, this case leads to is_defined function for this LXC returning false, since the set_config_path function will set configfile property (which is checked for LXC existence) to config_path/[LXC_NAME]/[CONFIG_FILE_NAME] (e.g. /home/lxc/testcontainer/config/testcontainer/config) which does not exist.
In the end I concluded that set_config_path property is not full path to config file of specific container, but full path to overall directory with subdirectories for configuration of each container.
Is this just misleading documentation, or I misunderstood something?
Thank you for any help.
