Maynard, a new Discourse user, encountered an error during plugin installation: “Your Docker installation is not using a supported storage driver,” despite Discourse running fine. His docker info showed overlay2, which the launcher flagged as potentially unsupported. After Falco suggested running git pull followed by ./launcher rebuild app, the issue was resolved and the plugin installed successfully. Falco later explained that Docker 19.x changed the docker info output format, and while the Discourse Docker repo had already been updated to handle it, Maynard’s launcher was outdated — it checks storage compatibility before auto-updating, creating a catch-22. Stephen suggested the launcher should update itself first before checking compatibility, and sam encouraged him to implement that change. The root cause was a version mismatch between Docker and the launcher script, not an actual incompatibility of overlay2.
“Your Docker installation is not using a supported storage driver. If we were to proceed you may have a broken install. aufs is the recommended storage driver, although zfs/btrfs/overlay and overlay2 may work as well. Other storage drivers are known to be problematic. You can tell what filesystem you are using by running “docker info” and looking at the ‘Storage Driver’ line. If you wish to continue anyway using your existing unsupported storage driver, read the source code of launcher and figure out how to bypass this check.”
Have searched for the same message in this forum and I am not clear exactly what to do from the replies.
Docker info on my set-up gives overlay2.
Not sure how Discourse can install ok, then the plugin install/rebuild not work.
Between installation and the plugin install/rebuild attempt, I have only updated Discourse and docker manager as per a notification, and performed apt-get update and apt-get upgrade.
Can someone clarify whether overlay2 can work? Or whether aufs is needed? What exactly are the instructions I need to follow to get the plugin install working?
However, our launcher script checks for the storage compatibility before auto-updating. So people who have an old launcher and update docker before updating launcher can get into that state.