I succeeded in creating a container following a document on linuxserver.io to run the pydio-cells on the swag network.
But, during database configuration, pydio-cells failed to read mariadb and could no longer proceed with the installation process.
I tried similar things to the nextcloud installation method, but it was still unsuccessful.
I couldn’t find a log to refer to, so I couldn’t solve it by myself.
Ubuntu 18.04 LTS + Docker lastest version
Pydio-cells is applying swag reverse proxy.
Both mairadb container and pydio-cells container are connected to the swag network.
Here is the docker-compose docs used to create the container.
If there is a log that I can provide, I will.
It looks like they are in two separate compose yaml files, which means they are not in the same custom bridge network, therefore, pydio-cells cannot reach the mariadb container via address mariadb
Put them in the same compose yaml file so they can reach each other via container name as dns hostname
Pydio cells is very picky about how you’re accessing it.
If you set the external url to your domain, you’ll have to access at https://yapu.kr exactly. If you’re reverse proxying at a subdomain, you need to set the external url in pydio cells to the subdomains address.
Don’t access at port 8080 when using the donation as that’s not going through the reverse proxy