![]() ![]() You didn’t describe the fdisk entry you tried (you might post that and then people can evaluate if it should work) The only thing I think I might have gotten right on first read is that your RPi is a client. Your original post was confusing as heck, My question is: is there something wrong with the fstab entry and if so what or, alternatively, is there a better way than curlftpfs to get the server to mount at boot? ThanksĬurlftpfs#server_IP_address /mnt/local_mnt fuse allow_other,uid=1000,gid=1000,umask=0022 0 0 Machine wouldn’t boot at all, I had to access through Knoppix, # out fstab line for curlftpfs to get it going. I set up a root/.netrc file and I added the below to fstab to get the ‘mount at boot’ bit working and disaster struck. I tried to achieve this with curlftpfs, and got there in the end even though I had a problem with the password I was using and had to backtrack to a fairly basic one. Research tells me that I need to have the Server mounted at boot, so it appears as a drive that way, I’m told it will appear on the side bar. to actually appear) managed that but now cannot actually add sources because of the above problem. tMM was problematic in that I had to replace openJDK with real Java for want of a better term to actually get the side bar (left Hand side with places etc. I want to use a better media manager for my library the Pis use and have tried to use tiny MediaManager and MediaElch, but have struck the same problem for each – my server does not show up in the ‘Add Media Source’ box in either. I have a FTP link to it set up in Dolphin through which I can access the server and treat it just like another hard drive, moving files, opening files etc. Using Leap 42.1 - I have a server I use with my Raspberry Pis for my media. This is done by passing the user ID and group ID to the container via the USER_ID and GROUP_ID environment variables.I’ve been trying to do this for a week or so now. To avoid any problem, you can specify the user tinyMediaManager should run as. This could prevent the container from properly accessing files and folders on the shared volume and vice versa. For example, the user within the container may not exist on the host or does not match the right user on the host. When using using data volumes (-v flags for /data and media), permissions issues can occur between the host and the container (tinyMediaManager). See below for an example how to use this. ID of the group tinyMediaManager runs as. This image offers some special configuration parameters which can be passed to docker by using environment variables Variable You need read/write access to all mapped volumes! Configuration If you do not map this out of the container, all your data/settings will be lost on an upgrade of tinyMediaManager /data: where all local data of tinyMediaManager will be stores.You should map the following folders to a volume/folder on the host: E.g.:ĭocker run \ -name =tinymediamanager \ -p 4000:4000 \ -v :/data \ -v :/media/movies \ -v :/media/tvshows \Īfter starting the container, you can access tinyMediaManager via Data volumes Map local volumes/folders/mounts to /media/xxx where all media will be accessed.Map a local volume/folder to /data where all local data from tinyMediaManager is stores (like data, logs, cache and backups). ![]()
0 Comments
Leave a Reply. |