Fix: mariadb needs root@"IP" to access database in container #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ined here: https://stackoverflow.com/questions/61950105/docker-doesnt-set-mariadb-password MySQL user is defined by username and host that request come from. For example, there is three different user [email protected], root@localhost and wildcard root@%. If you set MYSQL_ROOT_PASSWORD env in docker-compose file, your mariadb will set password for user root@%, not password for user root@localhost. But when you try to test password of mariadb, you use sudo docker exec -it docker_db_1 mysql -u root -p command, it mean mariadb-client in container will use user root@local (without password) to access mariadb-server, not user root@%(that have password you set before). So if you want to test password you set for that user, use that command: docker run -it mariadb mysql -u root -h MARIADB-CONTAINER-IP -p
|
Thank you! |
|
Nice, thank you! Its not a big thing, but i needed some time to adapt your solution to my database, so i thought i'd share that! |
|
Hi @Edukarl , now I got some time to check your commit. On my setups, the mariadb and mysql Passwort of root@localhost is set up correctly. But perhaps it is because the setup is running for years now and they changed the up the setup process, when you are running a clean mysql or mariadb container. Thank you! cheers |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As i got access denied with your script for a Backup of paperless-mariadb i found this from https://stackoverflow.com/questions/61950105/docker-doesnt-set-mariadb-password :
MySQL user is defined by username and host that request come from. For example, there is three different user [email protected], root@localhost and wildcard root@%.
If you set MYSQL_ROOT_PASSWORD env in docker-compose file, your mariadb will set password for user root@%, not password for user root@localhost.
But when you try to test password of mariadb, you use sudo docker exec -it docker_db_1 mysql -u root -p command, it mean mariadb-client in container will use user root@local (without password) to access mariadb-server, not user root@%(that have password you set before).
So if you want to test password you set for that user, use that command:
docker run -it mariadb mysql -u root -h MARIADB-CONTAINER-IP -p