Well, it’s not really resolved just yet, right? I set up a new Discourse instance today and found that I had to create a new file:
/etc/docker/daemon.json
with the contents
{
"storage-driver": "overlay2"
}
So, that’s the temporary fix from the maintainer’s perspective. I’m glad to hear that the problem should go away within the next release or two.