If this was AI I’d have expected HB IS NOT YOUR FIEND56

So is the issue that your extra drive mounts to /storage, but that happens after Docker has already started and taken over the directory, so the mount fails? Normally I’d expect it to happen in the other order. Is this a weird race condition?

This might be a good thing to run through with ChatGPT- there are probably ways to delay the Docker container start, but maybe there’s a more significant misconfiguration you can deal with.

Is Docker starting up and one of the containers mounts a volume to a /storage folder on the host? That could explain it but I’m not super clear on all that’s going on in your system.

Quick test: disable auto start on all your containers and restart and see if it recurs.

That falls under WRONG. Lack of consent is WRONG but there’s also nothing worse than documentation that is WRONG.