Nextcloud version (eg, 20.0.5): pulling latest with docker
Operating system and version (eg, Ubuntu 20.04): docker on synology NAS
Apache or nginx version (eg, Apache 2.4.25): Apache 2.4 running as a package on NAS
PHP version (eg, 7.4): 7.3 and 7.4 installed in package center on NAS
ISSUE: cannot even get nextcloud to start up
I really could use some help here. I don’t know where I have gone wrong.
I have managed to get all the containers in my docker-compose.yml file up and running but nextcloud is the ONLY container that will not show up when I try to access it from NETWORK-IP:8082 (8080 was attached to something else but I’ve also tried this with 8080 and it did nothing)
When it sat with my main compose file (with other services like freshrss, youtube-dl), it looked like this:
mariadb: image: mariadb container_name: mariadb command: --transaction-isolation=READ-COMMITTED --binlog-format=ROW --innodb-read-only-compressed=OFF restart: always volumes: - /volume1/docker/mariadb:/var/lib/mysql environment: MYSQL_ROOT_PASSWORD: PASSWORDHERE MYSQL_USER: nextcloud MYSQL_PASSWORD: CREATE-PASSWORD-HERE MYSQL_DATABASE: nextcloud nextcloud: image: nextcloud restart: always container_name: nextcloud ports: - 8082:80 links: - mariadb environment: - MYSQL_PASSWORD=CREATE-PASSWORD-HERE - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud - MYSQL_HOST=mariadb volumes: - nextcloud:/var/www/html volumes: nextcloud: mariadb:
When I run docker-compose up -d and then go to NETWORK-IP:8082, it just says unable to connect.
Things I have tried, but did not work
Spinning MariaDB and Nextcloud in its own separate stack. I thought maybe compose versioning could be an issue since most guides for this use version 2 and my own main compose file is version 3.
complete docker-compose down and up
checked that both mariadb and nextcloud containers were sitting in the same docker network
Where have I gone wrong?
Thank you for any help in advanced.