Following up on Overlayfs to Overlay2, Failed on Fresh Installation, storage driver
I whined over on
And it seems that overlay2 is not installed anymore:
So I guess either Discourse needs to move to a new image thingy?
AI-generated summary
The discussion revolves around the deprecation of overlay2 as the default storage driver in Docker, which is no longer installed by default in newer versions. pfaffman notes that this change is intentional, as overlay2 is deprecated and Docker Engine v29 no longer includes it. sam references a previous resolution, but mcmcclur clarifies that the issue remains unresolved, requiring manual configuration of the storage driver in /etc/docker/daemon.json. pfaffman confirms the fix was recently merged, while mcmcclur shares that their instance was set up earlier, suggesting they may have avoided the issue due to timing.
1 Like
wasn’t this resolved here?
2 Likes
Yes! I started a new topic, since the other one had been closed, I think, but this one didn’t get picked up.
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.
When? This just got merged. About 3 hours ago.
1 Like
My DigitalOcean history says I set it up 11 hours ago, or about 10:30 AM EST. I guess I got lucky!
I had updated the discourse-math plugin and was trying to figure out how to install it into my production Discourse. I didn’t want to mess up the instance that I actually use so I set up another.
1 Like
This topic was automatically closed after 22 hours. New replies are no longer allowed.