Closed pide2000 closed 1 year ago
I had similar issue and didn't quite understand what happened, but managed to find a workaround. Not sure if this is going to work for you though.
I removed seafile user with DROP USER 'seafile'@'%.%.%.%'
, made sure that there were no other user named seafile
in db and started again. And it was successful.
My guess is that you might have accidentally changed the password or maybe db data folder was not clean.
As a side note: you can format blocks of code with triple backticks, instead of one.
yes, the bootstrapping or whatever is fucking up the database's grant tables. what it did to solve this was adding a file /docker-entrypoint-initdb.d/seafile.sql
to the db container:
GRANT ALL ON *.* TO 'root'@'%';
FLUSH PRIVILEGES;
mind that this is only applied when no database exists yet.
I've started seafile docker using docker-compose
log says:
waiting for mysql server to be ready: %s (1130, "Host '172.20.0.4' is not allowed to connect to this MariaDB server")
My docker-compose file looks like this: `version: '2.0' services: db: image: mariadb:10.1 container_name: seafile-mysql environment:
seafile-net
memcached: image: memcached:1.5.6 container_name: seafile-memcached entrypoint: memcached -m 256 networks:
seafile-net
seafile: image: seafileltd/seafile-mc:latest container_name: seafile ports:
- "443:443" # If https is enabled, cancel the comment.
volumes:
networks: seafile-net:`