Martin Melka

To add to this, the script above can be added to the `/docker-init.db/` directory (in your own Dockerfile based on this image) and it will be executed automatically on startup....

Oops, sorry.

I am seeing this error when I enable opcache preloading in my project. Opened a PR that should fix this with more info.

Could you confirm that I understand the function of `IteratorAssembler` correctly? There is not much documentation in the docs nor the code, but this is what I think it is...

Thank you for the extensive answer, @veewee. Much appreciated! > 1. Not exactly: you could use a regex as in the example above or check if you can use anything...

Looking at the metrics, running out of memory seems to be the reason this started happening in the first place (around midnight from 14th to 15th Sep), but not anymore....

After increasing the memory from 16 to 32 GB, the same thing keeps happening, kubelite keeps restarting. Noticed a bunch of http timeouts in the kubelite logs though: ``` microk8s.daemon-kubelite[976]:...

Worth a try. I upgraded all three nodes one by one, but the end result is the same. Still restarts. Here is the [`microk8s inspect`](https://github.com/canonical/microk8s/files/9598121/inspection-report-20220919_102245.tar.gz) after the full cluster upgrade...

I ran that inspect after I had already removed the third node from the cluster, that's why there are two nodes listed there, my apologies for making this more confusing....

Into where you are initializing the client ``` $client = Client::createChromeClient([], [], [ 'capabilities' => [ ChromeOptions::CAPABILITY => $chromeOptions, ], ]); ```