Closed PhMemmel closed 1 year ago
Uhm, @PhMemmel ,
have you you got it working? Sorry for the late reply but I cannot find anything causing that problem and both CI and local runs say this is working with 400 and 4.1dev (master) perfectly.
If there is any other detail able to make us reproduce the problem, great, but right now it seems that everything is working ok, so far.
Ciao :-)
Hi @stronk7, thank you picking up on this. I managed to get it back to work and simply forgot to close this issue, sorry for that. Unfortunately, too much time has passed since then so I do not really remember how I fixed it, but it was nothing related to the docker repo. Again thx and sry, Issue closed.
Thanks!
I saw this on current master
with a custom-compiled PHP 8.2 container from #248. Moodle (or its support packages) throws a lot of notices on 8.2. Swapping in a PHP 8.0 container resolved the issue.
Hi @mackensen, could https://github.com/moodlehq/moodle-php-apache/issues/174 be of any help?
Shortly a recent change in the PHP base image requires the user to be specified when creating soft links in the container: -u www-data
.
HTH, Matteo
Also, note that Moodle still doesn't support php82, it's WIP @ https://tracker.moodle.org/browse/MDL-76405
I've tried to run behat test with a clean moodle repository with master branch
I set
MOODLE_DOCKER_WWWROOT
to the moodle repo andMOODLE_DOCKER_DB
tomariadb
.Running behatinit is working perfectly. However, running
bin/moodle-docker-compose exec -u www-data webserver php admin/tool/behat/cli/run.php --tags=@block_search_forums
(just an example tag) leads to:This seems to be related to moodle 4.0. Switching to
MOODLE_311_STABLE
, rerunning behat init and executing the command above everything works without a problem.