[BUG] Exception: Not installed in /config/www/nextcloud/lib/base.php:284 #280
Comments
|
Follow-up : after some tinkering in my configuration & some reading of the nextcloud server source code, here's what I understood:
The first issue be can be easily fixed. The second is trickier. I'm considering use of |
|
I am facing the same issue. Been tinkering with it for a few nights - no success yet. Running the container on k3s, mounted volume is a bcache. |
|
I'm fairly confident the repeating of the error in the logs is because of the cron task that runs every 5 minutes I would be very curious if you could wipe your config folder for nextcloud (rename it if necessary) and then start a brand new container with a fresh empty config (don't copy in your php) and run through the setup in the web UI. |
I deleted the config folder and started a new pod. These are the container logs. |
It works, but that's the point : it is necessary to go through the web UI. This means I cannot chain transmission to nextcloud :
The solution from there seems to firstly spin the docker compose with mock parameters for transmission, install nextcloud, then stopping the containers and providing the real path for transmission before starting everything again; which is painful. I'm not sure if it's nextcloud default behavior not to install its instance, or if this is an issue with this image. Likewise, I'm not sure whether this image should mark the container "started" when nextcloud is not installed. However, what ultimately seems to work with me is to use a healthcheck ; I'm simply |
|
I have this issue with a fresh install but am unable to access the UI to finish the setup. Any ideas? |
|
Surely you'd want to create and set up nextcloud before letting any other app write stuff into what's meant to be the nextcloud data folder. You don't have to create and start transmission at the same time as nextcloud. You can create your pod or do compose up -d with just nextcloud (optionally with mariadb), set it up in the wizard, then add transmission into the yaml and update the pod ir do compose up -d again. It only affects brand new installs.
|
|
While I follow the logic, having to configure manually through a UI something which can also be configured through a text file is quite painful in my opinion. But then again, maybe this is something nextcloud should address (for the record, finding information about Regardless, adding a healthcheck was the right tool for me and I hope this issue will provide insight for others with a similar use case (as below). FROM lscr.io/linuxserver/nextcloud:latest
# pinging the nextloud instance will eventually trigger the installation process until ultimately returning a login page
HEALTHCHECK \
--interval=2m \
--retries=10 \
--start-period=10m \
--timeout=5s \
CMD curl --insecure --fail "https://localhost:443/login" || exit 1
However, if (as @aptalca & @Festlandtommy & others seem to point out) the image's standard behavior is to output error logs (because manual installation is required), I think it could be a nice addition to the documentation. |
|
I don't know why this worked, but it worked. FYI, you can add a healthcheck to your docker compose file if you have one: |
Is there an existing issue for this?
Current Behavior
When I run the container for the first time, it configures Nextcloud, but something (I don't know what) triggers an exception somewhere in the process.
I suspect this prevents the setup from completing normally: my
config/www/nextcloud/config/config.phpfile is not marked asinstalled => true.I have to manually edit the
autoconfig.phpfile I provided and then manually setup the admin account through the web UI. There, theautoconfig.phpfile is deleted, theconfig.phpfile is updated and everything runs normally.When looking at the logs, I see an exception and this stacktrace, which is repeated every 5 minutes or so:
Though I post from my mac, as it is the hardware I have most of the time at hand, I also reproduced this bug on my Debian machine.
It seems to me my issue is very similar to #230 ; @j0nnymoe suggested it could be a permission issue and to try with folders under the
/home/<user>path, but it was the case in both configurations on my side.As said in this issue as well as earlier, I use both a
config.phpand anautoconfig.phpfiles. Is there something wrong in my config ?Expected Behavior
I expect the Nextcloud setup to complete normally and my
config.phpto be updated accordingly.Thanks a lot for your hard work, dedication and support by the way ; I have discovered your containers recently and I must say I am extremely satisfied with how easy the setup becomes, thanks to them (also, rad docs).
Steps To Reproduce
./is the root of the repository:a. create
./config/www/nextcloud/config/autoconfig.phpand paste the contents belowb. also copy the
./nextcloud/config.phpas./config/www/nextcloud/config/config.php(this one is not ciphered)c. finally, at the repository root, create an
.envfile and paste the contents belowdocker-compose upand wait for a bitautoconfig.php:.env:Environment
CPU architecture
arm64
Docker creation
Used
docker-compose upon thisdocker-compose.yml:Container logs
The text was updated successfully, but these errors were encountered: