I would like to have my AIO setup completely setup without ever clicking anything on the web UI
So I would like to define a Next cloud admin, the domain etc. ina scripted way or as env / yaml variables.
And… I don’t get how to access nextcloud itself smh I can only reach the AIO interface… there’s nothing on the Apache port. (I didn’t click anything on the AIO webui, maybe that’s the reason)
I have a fully automated deployment using the snap package but am in need to switch to AIO now.
AiO is designed with scripting in mind. This is meant to be an easy installation method.
People looking to automate the installation better look at Docker community image.
This guide goes really far in term of automation (but there is still room for improvement 
) so help is welcome.
so there’s no writeup to deploy AIO in a single scripted run without the need to interact manually (or programmatically) with the web-ui. And instead just passing the domain and other options smh…
I’d really like to build upon AIO. I just need it’s setup to be fully automated.
I don’t know any, but maybe you’ll share yours once you’ve figured it out…
You may be able to use the manual installation as the basis for your script. I haven’t looked at it in detail, but at first glance the sample.conf file seems to allow you to predefine all the relevant parameters to get a working instance.
sadly this doesn’t work… it will not setup the admin user as deifned and will just offer the AIO interface on https:8080.
I tried by setting the port from 443 to 81 (I have a reverse-prox in front of it which i can use) also I would like to access it first internally using the ip and also not havign the AIO as promised…
I can’t speak regarding the AIO stack in this area, but the micro-services Docker image can easily be deployed in this manner (and that’s probably how many, perhaps even most, use it): GitHub - nextcloud/docker: ⛴ Docker image of Nextcloud
This is the entire point of the auto-config variables, secrets, and hooks support. See the README in that repository for directions and examples.
Are you sure you acutally tried the manual install as pointed out by @bb77? In case you use that, there should not be any AIO interface. See this compose file: https://github.com/nextcloud/all-in-one/blob/main/manual-install/latest.yml
exactly this. It doesn’t work the way it’s written there.
What does not work, can you be a bit more specific? Did you follow all-in-one/manual-install at main · nextcloud/all-in-one · GitHub?
yes I did follow that exactly…
and jep… only the AIO-Interface comes up.
I did this:
git clone https://github.com/nextcloud/all-in-one.git
cd all-in-one/manual-install
cp sample.conf .env
then I edited the .env:
DATABASE_PASSWORD=Iwillnotsharepasswordswiththeinternet
FULLTEXTSEARCH_PASSWORD=Iwillnotsharepasswordswiththeinternet
IMAGINARY_SECRET=Iwillnotsharepasswordswiththeinternet
NC_DOMAIN=nc.hereismypublicdomain.tld
NEXTCLOUD_PASSWORD=Iwillnotsharepasswordswiththeinternet
ONLYOFFICE_SECRET=Iwillnotsharepasswordswiththeinternet
RECORDING_SECRET=Iwillnotsharepasswordswiththeinternet
REDIS_PASSWORD=Iwillnotsharepasswordswiththeinternet
SIGNALING_SECRET=Iwillnotsharepasswordswiththeinternet
TALK_INTERNAL_SECRET=Iwillnotsharepasswordswiththeinternet
TIMEZONE=Europe/Berlin
TURN_SECRET=Iwillnotsharepasswordswiththeinternet
CLAMAV_ENABLED="no"
COLLABORA_ENABLED="yes"
FULLTEXTSEARCH_ENABLED="yes"
IMAGINARY_ENABLED="no"
ONLYOFFICE_ENABLED="no"
TALK_ENABLED="yes"
TALK_RECORDING_ENABLED="yes"
APACHE_IP_BINDING=0.0.0.0
APACHE_MAX_SIZE=10737418240 # This needs to be an integer and in sync with NEXTCLOUD_UPLOAD_LIMIT
APACHE_PORT=81 # Changing this to a different value than 443 will allow you to run it behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else).
COLLABORA_DICTIONARIES="de_DE en_GB en_US es_ES fr_FR it nl pt_BR pt_PT ru" # You can change this in order to enable other dictionaries for collabora
COLLABORA_SECCOMP_POLICY=--o:security.seccomp=true # Changing the value to false allows to disable the seccomp feature of the Collabora container.
INSTALL_LATEST_MAJOR=no # Setting this to yes will install the latest Major Nextcloud version upon the first installation
NEXTCLOUD_ADDITIONAL_APKS=imagemagick # This allows to add additional packages to the Nextcloud container permanently. Default is imagemagick but can be overwritten by modifying this value.
NEXTCLOUD_ADDITIONAL_PHP_EXTENSIONS=imagick # This allows to add additional php extensions to the Nextcloud container permanently. Default is imagick but can be overwritten by modifying this value.
NEXTCLOUD_DATADIR=/var/nextcloud/data # You can change this to e.g. "/mnt/ncdata" to map it to a location on your host. It needs to be adjusted before the first startup and never afterwards!
NEXTCLOUD_MAX_TIME=3600 # This allows to change the upload time limit of the Nextcloud container
NEXTCLOUD_MEMORY_LIMIT=6144M # This allows to change the PHP memory limit of the Nextcloud container
NEXTCLOUD_MOUNT=/mnt/ # This allows the Nextcloud container to access directories on the host. It must never be equal to the value of NEXTCLOUD_DATADIR!
NEXTCLOUD_STARTUP_APPS="deck" # Allows to modify the Nextcloud apps that are installed on starting AIO the first time
NEXTCLOUD_TRUSTED_CACERTS_DIR=/usr/local/share/ca-certificates/my-custom-ca # Nextcloud container will trust all the Certification Authorities, whose certificates are included in the given directory.
NEXTCLOUD_UPLOAD_LIMIT=10G # This allows to change the upload limit of the Nextcloud container
REMOVE_DISABLED_APPS=yes # Setting this to no keep Nextcloud apps that are disabled via their switch and not uninstall them if they should be installed in Nextcloud.
TALK_PORT=3478 # This allows to adjust the port that the talk container is using.
UPDATE_NEXTCLOUD_APPS="no" # When setting to "yes" (with quotes), it will automatically update all installed Nextcloud apps upon container startup on saturdays.
logs:
docker compose up -d
[+] Running 1/1
✔ Container nextcloud-aio-mastercontainer Started 0.5s
root@nc:/opt/all-in-one/manual-install# docker compose logs
nextcloud-aio-mastercontainer | Trying to fix docker.sock permissions internally...
nextcloud-aio-mastercontainer | Adding internal www-data to group ping
nextcloud-aio-mastercontainer | ....+....+.....+...+.........+......+++++++++++++++++++++++++++++++++++++++++++++*..+..+++++++++++++++++++++++++++++++++++++++++++++*.................+.+......+.................+..........+.....+...+.........+................+..+...+....+........+.+.....+................+..............+.+.....................+..............+......+.......+......+.........+..+.........+.+........+...+...+.+......+...+.................+...+...................+...+...........................+......+............+..+.+..+.......+......+.........................................+....+.................+............+......+.........+......+........................+.......+...+...+........+............+...+....+......+......+........+...+...................+...+...........+.+......+.........+...+...........+......+.........+....+..+.+..............+......+...+....+......+.........+..+....+............+.....+...+.......+............+......+...........+...+.+..............+...............+.+...............+............+.....+....+...+..+.........+.......+...+.........+..+.+...+..+..................+....+...+........+....+.................+....+..+...+.+........+.......+...........+.......+.....+.+..+.........+................+.........+......+...+.....+.........+...+...+......+.....................+..........+..+.+......+........+......................+...+......+......+........+............+.+.....+..........+............+........+.......+..+....+...............+......+...+..+...+.+..............+.+.....+.+...+...+.................................+...........+......+...+.+..............+.........+.......+++++
nextcloud-aio-mastercontainer | .+.........+...+.....+......+..........+..+++++++++++++++++++++++++++++++++++++++++++++*.....+++++++++++++++++++++++++++++++++++++++++++++*......+...+...+..............+.......+......+.....+............+.+..............+...+.......+..+..........+...+...+.....+.......+.....+.....................+.......+..+..........+..+........................+.+........+...+....+...+...........+....+......+...........+...+.+..+..........+........+....+...+...+......+.....+.........+......................+.....+.......+.....+.+....................+............+++++
nextcloud-aio-mastercontainer | -----
nextcloud-aio-mastercontainer | Initial startup of Nextcloud All-in-One complete!
nextcloud-aio-mastercontainer | You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
nextcloud-aio-mastercontainer | E.g. https://internal.ip.of.this.server:8080
nextcloud-aio-mastercontainer | ⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
nextcloud-aio-mastercontainer |
nextcloud-aio-mastercontainer | If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
nextcloud-aio-mastercontainer | https://your-domain-that-points-to-this-server.tld:8443
nextcloud-aio-mastercontainer | [Wed Sep 11 19:03:50.310930 2024] [mpm_event:notice] [pid 151:tid 151] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.1 configured -- resuming normal operations
nextcloud-aio-mastercontainer | [Wed Sep 11 19:03:50.311017 2024] [core:notice] [pid 151:tid 151] AH00094: Command line: 'httpd -D FOREGROUND'
nextcloud-aio-mastercontainer | [11-Sep-2024 19:03:50] NOTICE: fpm is running, pid 161
nextcloud-aio-mastercontainer | [11-Sep-2024 19:03:50] NOTICE: ready to handle connections
nextcloud-aio-mastercontainer | {"level":"info","ts":1726081430.3337758,"msg":"using config from file","file":"/Caddyfile"}
nextcloud-aio-mastercontainer | {"level":"info","ts":1726081430.335575,"msg":"adapted config to JSON","adapter":"caddyfile"}
nextcloud-aio-mastercontainer | Initial startup of Nextcloud All-in-One complete!
nextcloud-aio-mastercontainer | You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
nextcloud-aio-mastercontainer | E.g. https://internal.ip.of.this.server:8080
nextcloud-aio-mastercontainer | ⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
nextcloud-aio-mastercontainer |
nextcloud-aio-mastercontainer | If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
nextcloud-aio-mastercontainer | https://your-domain-that-points-to-this-server.tld:8443
nextcloud-aio-mastercontainer | [Sun Sep 15 18:44:03.298690 2024] [mpm_event:notice] [pid 145:tid 145] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.1 configured -- resuming normal operations
nextcloud-aio-mastercontainer | [Sun Sep 15 18:44:03.298928 2024] [core:notice] [pid 145:tid 145] AH00094: Command line: 'httpd -D FOREGROUND'
nextcloud-aio-mastercontainer | [15-Sep-2024 18:44:03] NOTICE: fpm is running, pid 155
nextcloud-aio-mastercontainer | [15-Sep-2024 18:44:03] NOTICE: ready to handle connections
nextcloud-aio-mastercontainer | {"level":"info","ts":1726425843.32781,"msg":"using config from file","file":"/Caddyfile"}
nextcloud-aio-mastercontainer | {"level":"info","ts":1726425843.3298922,"msg":"adapted config to JSON","adapter":"caddyfile"}
there is nothign when I try to access ports 80 / 8443 but the AIO interface comes up on 8080…
It looks like you missed this after editing the env file:
Now copy the provided yaml file to a compose.yaml file by running
cp latest.yml compose.yaml.Now you should be ready to go with
sudo docker compose up.
oh yes… thx!
now I’m sitting on this step:
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
nextcloud-aio-nextcloud-1 | nc: getaddrinfo for host "nextcloud-aio-talk-recording" port 1234: Try again
nextcloud-aio-nextcloud-1 | waiting for Talk Recording to become available...
So you should check why talk-recording is not starting
Did you enable the container with --profile talk-recording?
yes, that was it…
I was so focused on setting up my custom stuff I scripted in occ that I didn’t even follow the simple writeup correctly…
I’m still not abel to get it running though:
nextcloud-aio-nextcloud-1 | The initial Nextcloud installation failed.
nextcloud-aio-nextcloud-1 | Please reset AIO properly and try again. For further clues what went wrong, check the logs above.
nextcloud-aio-nextcloud-1 | See https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance
nextcloud-aio-nextcloud-1 | Connection to nextcloud-aio-redis (172.18.0.5) 6379 port [tcp/redis] succeeded!
nextcloud-aio-nextcloud-1 | The initial Nextcloud installation failed.
nextcloud-aio-nextcloud-1 | Please reset AIO properly and try again. For further clues what went wrong, check the logs above.
nextcloud-aio-nextcloud-1 | See https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance
nextcloud-aio-nextcloud-1 | The initial Nextcloud installation failed.
nextcloud-aio-nextcloud-1 | Please reset AIO properly and try again. For further clues what went wrong, check the logs above.
nextcloud-aio-nextcloud-1 | See https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance
nextcloud-aio-nextcloud-1 | + '[' -f /dev-dri-group-was-added ']'
nextcloud-aio-nextcloud-1 | ++ find /dev -maxdepth 1 -mindepth 1 -name dri
nextcloud-aio-nextcloud-1 | + '[' -n '' ']'
nextcloud-aio-nextcloud-1 | + set +x
nextcloud-aio-nextcloud-1 | Connection to nextcloud-aio-redis (172.18.0.5) 6379 port [tcp/redis] succeeded!
nextcloud-aio-nextcloud-1 | The initial Nextcloud installation failed.
nextcloud-aio-nextcloud-1 | Please reset AIO properly and try again. For further clues what went wrong, check the logs above.
nextcloud-aio-nextcloud-1 | See https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance
nextcloud-aio-nextcloud-1 | + '[' -f /dev-dri-group-was-added ']'
nextcloud-aio-nextcloud-1 | ++ find /dev -maxdepth 1 -mindepth 1 -name dri
nextcloud-aio-nextcloud-1 | + '[' -n '' ']'
nextcloud-aio-nextcloud-1 | + set +x
nextcloud-aio-nextcloud-1 | Connection to nextcloud-aio-redis (172.18.0.5) 6379 port [tcp/redis] succeeded!
nextcloud-aio-nextcloud-1 | The initial Nextcloud installation failed.
nextcloud-aio-nextcloud-1 | Please reset AIO properly and try again. For further clues what went wrong, check the logs above.
nextcloud-aio-nextcloud-1 | See https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance
nextcloud-aio-notify-push-1 | Waiting for Nextcloud to start...
nextcloud-aio-nextcloud-1 | + '[' -f /dev-dri-group-was-added ']'
nextcloud-aio-nextcloud-1 | ++ find /dev -maxdepth 1 -mindepth 1 -name dri
nextcloud-aio-nextcloud-1 | + '[' -n '' ']'
nextcloud-aio-nextcloud-1 | + set +x
nextcloud-aio-nextcloud-1 | Connection to nextcloud-aio-redis (172.18.0.5) 6379 port [tcp/redis] succeeded!
nextcloud-aio-nextcloud-1 | The initial Nextcloud installation failed.
nextcloud-aio-nextcloud-1 | Please reset AIO properly and try again. For further clues what went wrong, check the logs above.
nextcloud-aio-nextcloud-1 | See https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance
nextcloud-aio-notify-push-1 | nc: getaddrinfo for host "nextcloud-aio-nextcloud" port 9001: Try again
nextcloud-aio-notify-push-1 | Waiting for Nextcloud to start...
nextcloud-aio-notify-push-1 | nc: getaddrinfo for host "nextcloud-aio-nextcloud" port 9001: Try again
nextcloud-aio-notify-push-1 | Waiting for Nextcloud to start...
nextcloud-aio-notify-push-1 | nc: getaddrinfo for host "nextcloud-aio
the linked how-to isn’t usign docker compose so I tried removing the install using:
cd /opt/all-in-one/manual-install
docker compose down -v --remove-orphans --timeout 0
docker rm -f $(docker ps -aq)
docker compose down -v --remove-orphans --timeout 0
redeploying it results in the same error. is there a way to see more?
idk what I dont delete with those commands. but completely setting up a fresh vm works.
maybe you know how to check in a script if the setup is completely done?
one idea was to check if the logs are staying the same, but for which amount of time… I would love to have an approach which works no matter which services I add. so i can do my additional steps afterwards.
You could check if the login page is reachable via curl for example
but is it only reachable when everything is setup already?