Hello! I’m working on a new-to-me site that is currently running Kirby 3.
Our Kirby is now running in a docker container which is deployed on a kubernetes cluster. To persist our data, we have two PVCs for content and accounts. These are using (as I have been told) EXT4 as filesystem.
I’ve discovered two issues:
- We now have a unlisted page “lost+found” in the backend.
- The initial installation did not work, instead of sending me to
panel/installation
, I was immediatly redirected topanel/login
because there was already that folder inside ofsite/accounts
and it was interpreted as an existing user.
The folder seems to be generated by Linux and can’t be deleted, as far as I’ve been researching by now. Now I’m not sure if this is a problem on Kirbys side or if I have to talk to Ops again for a solution.
So for now I’m just looking for some input. If this is a kirby-problem I’m happy to write an issue on Github.