-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
PermissionError: No folder could be found for config on update #400
Comments
Happening the same to me after update. |
Turns out it was storage space for me, fixing that sorted things out |
I have 160 Gb of free space where Maloja sits, not a storage issue for me.
|
Is your |
I've set all my containers to use my admin user, so it reflects 998:100. If now it's not accessible, something changed in the code, it worked fine for at least a year without me touching anything and Watchtower updating when legit.
The folder /rules is present, but not seen as 777 and it's empty. Timestamp says created 02/06/2023, so one and a half year ago. Never given problems.
|
Just to try, I have |
I can only really imagine permissions errors, not sure why it would change after an update. Is the sub-directory |
I have chmodded to -R 777 rules/ and all its contents. EDIT
|
Could you delete all the files from inside |
No, it doesn't solve.
Also both |
Alright guess a redeploy it is then, you need your |
Yes, a complete erase + backup-restore did the trick, it works now. Wonder what happened between updates. Thanks! |
Just updated to the latest image, logs:
compose.yaml
The text was updated successfully, but these errors were encountered: