But the containers cannot see what’s in those folders nor write to them.Īt this point, I am working just with Bazarr, Radarr, and Sonarr, since they are so similar or I would have just went to one container. it’s the containers that are having problems. It seems that Docker itself can use them fine. Then I found you could set docker’s API to be monitored from a remote Portainer, so I deleted that one. I’ve changed up things a bit, Portainer after a couple of hiccups started working. I cannot figure out why they cannot write. VirtualBox is running under my user account. Most of my containers are running on my dedicated Docker machine, but those that need access to lots of storage will be on this machine. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |