I followed the docker compose example for installation (with ngingx proxy, apache, mariadb). A notable difference is that I’m using a bind mount for the nextcloud data directory, rather than having docker manage the volume.
My Problem:
Under /settings/admin/serverinfo, usually the used/available disk space is displayed in a neat graphic:
The API responsible for this seems to be /apps/serverinfo/api/v1//diskdata?format=json from the serverinfo app, and it returns an empty array in my installation.
The API call seems to call the getDiskInfo PHP funtion in my case. There we can see that it uses df -TPk to find disks and their usage.
When I execute this within my nextcloud container, it shows the disk space without any issues. But the disk is mounted under /etc/hosts, and getDiskInfo funtion skips anything that is mounted under /etc/hosts.
So I have several questions:
Why is it skipping disks mounted under /etc/hosts?
Is my disk even supposed to be mounted there?
Any ideas for workarounds?
Just started a few days ago but still, this is my take from what i found out.
For me it only sees the /dev/sda /mnt/nextcloud (data path set to /mnt/nextcloud/data)
I moved my data folder from /dev/sdb2 (default snap location)
First it displayed the used/available space from /dev/sdb2.
Now it displays the used/available space from /dev/sda (1 large ext4 partition)
My guess it just shows how much space is left on the volume the data dir is placed?
In ubuntu you can use LVM to make a large volume and keep adding to it.
ps.
Just wondering, i’m using 30.4 and in my system page it doesn’t show DNS or that nice circle for the drive space?
My guess it just shows how much space is left on the volume the data dir is placed?
Yes I think so too, and it works fine for me. My issue is only that the circle graphic is missing. I assume it is missing for you for the same reason. Can you run df -TPk from inside your nextcloud app container to confirm?
Currently running Nextcloud bare metal, after fighting Docker and Snap i decided to go the ‘old ways’ the installation on Snap or Docker seem easy, when it comes to configuring however… i don’t like it, how many posts i found relating to running occ from docker/snap…
Yes the bare metal Nextcloud takes some more work, but most of the help information is more focused towards it from what i can tell. The guides/manuals are easier to use.
Also when looking at my “Nextcloud/admin/system” page it looks like this now :
(zoomed out to show everything)
No more Snap errors (apparmor denied), easier editing files, so far no errors with OCC commands (still want to make it available everywhere from console and web occ).
CPU speed/temperature disk space, cpu, network speeds/interfaces etc.
My overall experience has improved switching to a bare metal installation.
Adguard and Wireguard are also running fine now and in combination with Nextcloud.