on rpi5

 

Host Type - Debian 12

Install type - nextcloud-releases/all-in-one docker

 

step 1.

sudo docker volume create nextcloud_aio_mastercontainer

 

step 2.

run ok

sudo docker run \
--init \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 80:80 \
--publish 8180:8080 \
--publish 8443:8443 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
ghcr.io/nextcloud-releases/all-in-one:latest

 

sudo docker volume ls

output

DRIVER    VOLUME NAME
local     0f7d561bdb336575805144b273c70ad44530d074d06165c7e4d9233a8abdd414
local     a74265c4a4b21badd2cefb27d319296bb7338e15b38ac0aaa4b36c1b2f195c38
local     nextcloud_aio_mastercontainer

 

sudo docker volume inspect nextcloud_aio_mastercontainer | grep "Mountpoint"
output
        "Mountpoint": "/var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data",

 

sudo ls -la /var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data
total 24
drwxrwxrwx 6 root     root     4096 Nov 11 05:22 .
drwx-----x 3 root     root     4096 Nov 11 05:06 ..
drwxrwx--- 3 www-data www-data 4096 Nov 11 05:22 caddy
drwxrwx--- 2 root     root     4096 Nov 11 05:22 certs
drwxrwx--- 2 www-data www-data 4096 Nov 11 08:43 data
drwxrwx--- 2 www-data www-data 4096 Nov 11 05:29 session

 

History of debug logs

1.

sudo docker run  \
  --name nextcloud-aio-mastercontainer \
  --restart unless-stopped \
  -p 80:80 \
  -p 8180:8080 \
  -p 8443:8443 \
  -v /var/run/docker.sock:/var/run/docker.sock:ro \
  -v /datadocker/nextcloud/nextcloud-aio/data:/mnt/docker-aio-config \
  ghcr.io/nextcloud-releases/all-in-one:latest

output

Trying to fix docker.sock permissions internally...
Creating docker group internally with id 992
WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No memory limit support
WARNING: No swap limit support
It seems like you did not give the mastercontainer volume the correct name? (The 'nextcloud_aio_mastercontainer' volume was not found.)
Using a different name is not supported since the built-in backup solution will not work in that case!

 

sloved

sudo docker volume create nextcloud_aio_mastercontainer

2.

It seems like you did not give the mastercontainer the correct name? (The 'nextcloud-aio-mastercontainer' container was not found.)
Using a different name is not supported since mastercontainer updates will not work in that case!
If you are on docker swarm and try to run AIO, see https://github.com/nextcloud/all-in-one#can-i-run-this-with-docker-swarm

 

3.

http://192.168.2.125:8180/login

output

Bad Request
Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Apache/2.4.65 (Unix) Server at localhost Port 8080

sloved

https://192.168.2.125:8180/login

4.

Log in using your Nextcloud AIO passphrase

sloved

If you have somehow lost the passphrase that is used for the AIO interface, you can reobtain it by running sudo docker exec nextcloud-aio-mastercontainer grep password /mnt/docker-aio-config/data/configuration.json

# sudo docker exec nextcloud-aio-mastercontainer grep password /mnt/docker-aio-config/data/configuration.json
    "password": "lanky clumsily shredding compare backhand twirl bouncing wildfire"

 

useful links

http://localhost:4999/boards/topic/48316/nextcloud#69743

Comments


Comments are closed