Closed synergiator closed 4 years ago
@synergiator thanks for reporting the issue. Yes, cmk needs to create its config directory at $HOME/.cmk where it stores config, profiles etc. When running just make sure your user/process has access to allow cloudmonkey to create and manipulate its config/history/profile/cache files. It could be a permission issue (for example run: sudo chown -R
Can you also share your platform and OS (such as x86_64, Linux) etc. Thanks.
Any update @synergiator probably the ~/.cmk is not owned by your user?
hi there @rhtyd I think yes, this has been a constellation where the path was created by Docker as I used cmk inside a container mounted to local path. Can't reproduce anymore. The intention of this issue was just to maybe have a more explicit error message, telling the user in such occasion which files/folders could not be accessed exactly.
Thanks closing as you can't reproduce this anymore. I've added an issue to add check for file permission and proper error msg: https://github.com/apache/cloudstack-cloudmonkey/issues/68
Just discovered this exception:
Which files does
cmk
need to lock here?Workaround: sudo