Operating system and version (e.g., Ubuntu 24.04):
Docker on debian (VM on Proxmox)
OMV 7 as NFS Share Server
********
Hello,
I want to install a new NC AIO (docker compose) with data backup from old instance.
I want to connect a NFS file share on OMV 7 for the data directory.
I did the following steps:
mount the NFS File on the docker host ( /mnt/nextcloud/ncdata ) - there is an subfolder /data)
set the chmod (chmod 755 -R /mnt/nextcloud)
set the ownership ( chown -R 33:0 /mnt/nextcloud ) …also tried chown -R 33:33 /mnt/nextcloud)
at compose.yaml NEXTCLOUD_DATADIR: /mnt/nextcloud/ncdata/data
No Error in the Docker console during start with hints on a share/volume problem.
Starting the from Backup Recover the NFS share keeps empty and the docker file system runs into "no space left on device"
I also tried to create volume nextcloud_aio_nextcloud_datadir with the local mount and also with direct nfs share connection.
Any idea how to look why the container does not use the NFS share ?
name: nextcloud-aio # Add the container to the same compose project like all the sibling containers are added to automatically.
services:
nextcloud-aio-mastercontainer:
image: ghcr.io/nextcloud-releases/all-in-one:latest # This is the container image used. You can switch to ghcr.io/nextcloud-releases/all-in-one:beta if you want to help testing new releases. See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel
init: true # This setting makes sure that signals from main process inside the container are correctly forwarded to children. See https://docs.docker.com/reference/compose-file/services/#init
restart: always # This makes sure that the container starts always together with the host OS. See https://docs.docker.com/reference/compose-file/services/#restart
container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work
- /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the applicable documentation. If adjusting, don’t forget to also set ‘WATCHTOWER_DOCKER_SOCKET_PATH’!
network_mode: bridge # This adds the container to the same network as docker run would do. Comment this line and uncomment the line below and the networks section at the end of the file if you want to define a custom MTU size for the docker network
ports:
- 8070:8080 # This is the AIO interface, served via https and self-signed certificate. See https://github.com/nextcloud/all-in-one#explanation-of-used-ports
environment: # Is needed when using any of the options below
APACHE_PORT: 11000 # Is needed when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
APACHE_IP_BINDING: 0.0.0.0 # Should be set when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else) that is running on the same host. See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
NEXTCLOUD_DATADIR: /mnt/nextcloud/ncdata/data # Allows to set the host directory for Nextcloud’s datadir. ??? Warning: do not set or adjust this value after the initial Nextcloud installation is done! See https://github.com/nextcloud/all-in-one#how-to-change-the-default-location-of-nextclouds-datadir
NEXTCLOUD_MOUNT: /mnt/ # Allows the Nextcloud container to access the chosen directory on the host. See https://github.com/nextcloud/all-in-one#how-to-allow-the-nextcloud-container-to-access-directories-on-the-host
volumes: # If you want to store the data on a different drive, see https://github.com/nextcloud/all-in-one#how-to-store-the-filesinstallation-on-a-separate-drive
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer # This line is not allowed to be changed as otherwise the built-in backup solution will not work
I suspect the problem is that your root partition only has 9,8G left but stores all docker images, volumes and the whole system. I would recommend to increase the root disk to at least 50G.
I think, that would not be my current problem, because I see, during the “recovery” the “borg-backup” container would write it in the container filesystem (yes than the 9,8GB are not enough), but it should write all the recovered data to the NEXTCLOUD_DATADIR: /mnt/nextcloud/ncdata/data and there are 100GB free… so my problem is, that the configured mount will not be used and I do not know where to find the error.
I read that in case of an problem, the AIO returns to a default “datadir” value and that seems to be the case…
No, it works as designed. The datadir indeed should be extracted onto the configured target. However the volumes and the images and other docker data is still stored in the configured Docker Root Dir, in your case on the very small root drive.