Oh… that’ll probably be in the docker container log. I’m not sure if I can dig back that far… probably not :(

Yep aarrrrrghhhh it’s at when the container is initialized. Too late T_T Maybe I can tell if I manage to start a separate instance, but I’m not sure if there’s enough hardware resources on my side to try. But I’ll open the ticket first regardless based on Crabby’s findings