![]() The final command to ping app/80 is different from the other “CLOSED” failures in that it spins for over a minute before failing. 127.0.0.1:6379> KEYS * (empty (/dev/null & echo "OPEN" || echo "CLOSED" (/dev/null & echo "OPEN" || echo "CLOSED" (/dev/null & echo "OPEN" || echo "CLOSED" (/dev/null & echo "OPEN" || echo "CLOSED" CLOSED redis-cli -a testPass Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. Additionally, I’ve tried running redis with a defined password to no avail.įor good measure I just retried using this updated docker-compose with some of your suggestions: version: '3'Ĭommand: redis-server -requirepass testPassįrom the command line of my redis redis-cli -a testPass ping Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. I’m not sure why I would need to publish the ports for in network communication though. You can find some examples of that on the forum.īack to my other failed attempts, I’ve tried adding a ports: section to the nc-redis service it did not help. ![]() ![]() Instead of expose, this should have a ports: setting like the others.Īlso I think since a particular version, you need to change the redis command to either disable authentication or provide a password. volume1/docker/nextcloud/config:/var/Unfortunately all the logs I’ve been able to find have been useless. MYSQL_USER_FILE=/run/secrets/mysql_user MYSQL_DATABASE_FILE=/run/secrets/mysql_db MYSQL_PASSWORD_FILE=/run/secrets/mysql_pw volume1/docker/nextcloud/database:/var/lib/mysql Here is my docker-compose.yml: version: '3'Ĭommand: -transaction-isolation=READ-COMMITTED -log-bin=binlog -binlog-format=ROW -innodb-read-only-compressed=OFF This the db container which is on the same network as the redis and nextcloud containers can ping without issue. Unfortunately ping is not installed with the nextcloud docker, but using /dev/tcp I’ve established that the nextcloud container cannot ping the redis container. However, once nextcloud attempts to use redis as the session handler the nextcloud site will spin until it times out.Īfter many hours of troubleshooting I think I’ve found the issue, but can’t figure out a fix. The same is true if I add the redis portion to my compose file, but exclude the REDIS_HOST env from the nextcloud service. When I create the instance without redis in my docker compose file I can bring up the nextcloud app without issue. I’m attempting to install nextcloud docker on my Synology 923+ inside portainer. ![]()
0 Comments
Leave a Reply. |