Jeff Geerling
Jeff Geerling
And https://www.jeffgeerling.com/sites/default/files/tutorial-images/tethering.jpg — from blog post https://www.jeffgeerling.com/tutorial/2009-06-17/tethering-your-iphone-your-mac-iphone-os-30
Hmm... looking in the access logs, it seems that there may be some weird request loop that goes on, maybe caused by CleanTalk, and maybe if the connection gets dropped...
That route comes from `\Drupal\comment\Controller\CommentController::commentApprove` and the token is a CSRF token set by the comment module.
This would make for a more flexible setup, though one difficulty with the approach (for one individual site) is that the title field is not universally unique, therefore it's possible...
I changed the title and I'll see how things fall out after the index is updated.
Finally found the root cause: dependency issue in the docker python library: https://github.com/docker/docker-py/issues/2842
See blog post: https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/
Note that this can have interesting results if it's in an environment with multiple replicas. See: https://github.com/geerlingguy/raspberry-pi-dramble/issues/139 It's fine for testing / evaluation purposes... but you really need a dynamic/environment-variable-driven...
In the Kubernetes world, it might be possible to avoid conflict using an `initContainer`. In that container, check if Drupal is installed. If so, exit. If not, run the install...
Does it work on the docker-debian11-ansible container? Could be an issue with cgroupsv2 depending on your host OS.