-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot find any of the supported PHP image extensions! #179
Comments
Btw, I had the exact same problems with the latest LS v3 Docker images... |
Hi, thanks for the hint. I'll have a look at it. I'm not using it on a daily basis anymore, so I rely on users to help me find issues like that. |
Hey, can you provide some more info on how to recreate this error? I did not see an error in the admin panel with a fresh build. |
Thanks for your feedback! I installed LS v6 and used an existing LS database structure from an old version. Just to make sure that this does not cause any trouble, I started another LS v6 docker container and connected it against a fresh, empty MySQL database. This is the create script that I used:
The database structure gets bootstrapped as far as I can see, but I am not able to sign in into the admin interface. I get the error message "Internal database authentication method is not allowed for this user". I then dropped the DB, created a new one and then ran the command
inside the docker container:
but I still can not log in with the admin account... Any suggestions? |
Hello everyone,
I installed a fresh copy of the Docker image
martialblog/limesurvey:6-apache
an after loggin in into the admin web UI I tried to upload an image. I get an error message:
Cannot find any of the supported PHP image extensions!
I was able to fix that by installing GD and ImageMagick into the running container, but my question is: why are these essential PHP libraries missing in this Docker image? Am I the only one with this kind of problem?
That's what I did to make it work:
Thanks, Marc
The text was updated successfully, but these errors were encountered: