I assume I should have tried this before deploying the discourse container: How to change the Docker storage driver – Webdock
Apparently it is possible to change the storage driver - contrary to what the host instructed me back when we deployed the container (which was to either edit the loader file or ignore the check)
Duh, now it is too late I’d assume.
Thanks anyway, if this is the cause of the issues, I guess it is user-wrongdoing. Mea culpa 