Right now, I’m running Portainer, Bazarr, Radarr, Sonarr, Syslog-ng, and I will be running BackupPC or UrBackup once I get the rest of them being able to write to the shared folders. It makes no difference if I run docker-compose with sudo or not. it’s just the Docker containers that can’t write to it.

I can read and write to the shared folders just fine from the VM machine using nano or whatever tool I need, and Docker itself can create any directory it needs on running docker-compose up -d. I have made my user a member of the vboxsf group (as well as the docker group so I don’t have to use sudo for everything Docker related). Now, Docker runs great but the containers cannot write to the shared folders I set up in VirtualBox. So I just cut out the middle-man and just created a Linux VM manually and running Docker in there. It’s a 2008 Mac Pro, so Docker for Mac isn’t possible. Unfortunately, there are some Docker containers I need to use that needs the storage on my file server. I have my main Docker server running Ubuntu Server natively.

I am setting up a Docker VM on my file server.

Shared folder permissions virtualbox