# Overlayfs zu Overlay2, fehlgeschlagen bei Neuinstallation, Speicher-Treiber

**URL:** https://meta.discourse.org/t/overlayfs-to-overlay2-failed-on-fresh-installation-storage-driver/389126
**Category:** Support
**Tags:** docker, install
**Created:** [20. November 2025 um 00:03 UTC](https://meta.discourse.org/t/overlayfs-to-overlay2-failed-on-fresh-installation-storage-driver/389126 "2025-11-20T00:03:23Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [21. November 2025 um 00:21 UTC](https://meta.discourse.org/t/overlayfs-to-overlay2-failed-on-fresh-installation-storage-driver/389126/6 "2025-11-21T00:21:47Z")

</div>

Wenn ich das richtig verstehe, müssen wir also auch nach `overlayfs` suchen und es einbeziehen?

PR dafür hier:

> <https://github.com/discourse/discourse_docker/pull/1014>
>
> new storage driver on by default, per:
> https://docs.docker.com/engine/storage/d…rivers/
> 
> containerd image store seems to report as overlayfs, so we should allow for this string as well.
> 
> Ref:
> https://meta.discourse.org/t/overlayfs-to-overlay2-failed-on-fresh-installation-storage-driver/389126

---

_[View the full topic](https://meta.discourse.org/t/overlayfs-to-overlay2-failed-on-fresh-installation-storage-driver/389126)._