

It sounds to me like one (or more) of your containers is referencing something on your storage drive, but Docker is loading before your drive gets mounted. When Docker sees that the folder its trying to access doesn’t exist, it creates it, blocking your drive from taking that name.
To fix it, you would need to make sure your storage drive is mounted before Docker starts, how you do that is down to you and your particular setup though.
Hmm funny how Sam Altman is one of the few people responsible for creating that problem and now he’s selling the solution to it