You should upgrade to MySQL 5.5.0 or later error #118
Comments
|
What does the server return when you execute |
|
|
I tried a simplified as possible standalone version: '2'
services:
mysql:
image: mysql:5.6
environment:
- MYSQL_ALLOW_EMPTY_PASSWORD=yes
pma:
image: phpmyadmin/phpmyadmin
depends_on:
- mysql
ports:
- '8100:80'
environment:
- PMA_HOST=mysql
- PMA_USER=rootHere is the up log: Still have the issue. |
See phpmyadmin/docker#118 Signed-off-by: Michal Čihař <michal@cihar.com>
|
Hmm, that looks completely okay. |
|
I'll pull your commit ASAP and give you a feedback, thanks. |
|
That commit won't fix anything, it's just added test for the code :-). You can workaround it by setting |
|
I tried with the following config files: <?php
$cfg['MysqlMinVersion']['internal'] = 0;Mounted like this: pma:
image: phpmyadmin/phpmyadmin
volumes:
- ./docker/conf/phpmyadmin.user.inc.php:/etc/phpmyadmin/config.user.inc.php:ro
depends_on:
- mysql
ports:
- '8100:80'
environment:
- PMA_HOST=mysql
- PMA_USER=rootAnd I have a lot of error, like those: Did I f*cked up something? 😄 |
|
Seems to be because of the Anyway, I tried: $cfg['MysqlMinVersion']['internal'] = 0;
$cfg['MysqlMinVersion']['human'] = '0.0.0';And this changes nothing, I still have the error... Can't you reproduce it with the provided |
See phpmyadmin/docker#118 Signed-off-by: Michal Čihař <michal@cihar.com>
|
I can reproduce it now. The problem is that you have set PMA_USER but not PMA_PASSWORD, what triggers bug in configuration checking code leading to not reported connection failure. I've adjusted the Docker container to set password to empty string in such case and I've also fixed handling of this situation on the phpMyAdmin side. To fix the error, just set |
|
Just tried with: version: '2'
services:
mysql:
image: mysql:5.6
environment:
- MYSQL_ALLOW_EMPTY_PASSWORD=yes
pma:
image: phpmyadmin/phpmyadmin
depends_on:
- mysql
ports:
- '8100:80'
environment:
- PMA_HOST=mysql
- PMA_USER=root
- PMA_PASSWORD=Changed nothing. |
|
Ah, there is another problem with handling empty values from environment. Looking for a fix.... So just don't set PMA_USER at all, and it will work with cookie auth. |
If environemnt variable is empty and is not part of $_ENV, the getenv (obviously) returns empty string, but we should use it. Fixes #118 Signed-off-by: Michal Čihař <michal@cihar.com>
|
Yeah... but I don't want cookie auth. :-) I have this configuration on dev env to get rid of this auth form and session limit and get access to this PMA at any time. BTW, FYI, this configuration always worked for me. Which change did break this part? |
|
The 4.7.0 has different handling of authentication configuration and it did trigger this. But the root cause is that Docker setup for no password was broken, it was just not visible before... |
|
So, will it works when I'll pull your last commit from docker hub with the initial docker-compose configuration? |
|
Yes, it should |
|
Indeed, this is now working. Thank you for the quick fix! 👍 |
Since the last pull, I have this error while trying to access PMA:
The problem is... I use it with MySQL... 5.6! \o/
Here is my
docker-compose.ymlfile (concerned part):Also tried with
phpmyadmin/phpmyadmin:4.6, same thing.Any idea of why?
The text was updated successfully, but these errors were encountered: