In the go file I place a simple call to the above start up script like this. The above sets up a link from the RAM filing system to that folder on the cache drive. So that it survives reboots and to save RAM I choose build it on the cache drive. The key detail is that Asset by default would place the database of scanned metadata from your music in the RAM filing system. # The path to the binaries changed after V5, so.Ĭd /mnt/cache/.AssetUPnP/Asset-R6-Linux-圆4-registered/bin # create a soft-link to the database on the cache drive # remove any folder contents (if present normally will just generate an error) # remove any old link (if just restarting Asset normally will generate an error) # At different times I have needed different locations. # I set this up twice, once in / and once in /root # AssetUPnP doesn't know about my cache drive, it uses a folder called /root/.dBpoweramp which would normally be in RAM so I need to creat a soft-link to redirect from there to the cache
ASSET UPNP USER MANUAL ARCHIVE
# Unpack the downloaded archive - change file name here to match downloaded archive file for AssetUPnP # should already be here, but just in case AssetUPnP folder I have a simple script derived from the one that the AssetUPnP guys have placed in their support forums for the Linux version. It's just an archive file that gets copied into that. I do the download under Windows, but it desn't matter. I don't want the download to change just because they've updated the program in case it breaks something. I prefer to do the download manually, then I always know which version is beng run. I have a paid license for AssetUPnP so I use the file that I download when I look up my order from the program creators.
ASSET UPNP USER MANUAL TRIAL
The URL that you have is correct for the trial version. In that folder I place the file that I download for the AssetUPnP Linux 64-bit version. is the old way of making the folder non-moveable. On my cache drive I create a folder called. usr/bin/docker: Error response from daemon: oci runtime error: container_linux.go:265: starting container process caused "exec: "/usr/bin/asset/bin/AssetUPnP": stat /usr/bin/asset/bin/AssetUPnP: no such file or directory". When I try to add the docker on the docker page in unraid I /usr/local/emhttp/plugins//scripts/docker run -d -name="Asset-UPNP" -net="host" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" sparklyballs/asset-upnpĪa619a608337f4e150e84b2702851aa06650c3facdb282fb12ca34d629b83a5f Is something wrong with the dockerfile or is it unraid 6.4.0 which I'm currently running? The docker doesn't seem to get build and when running it it shows:ĭocker: Error response from daemon: oci runtime error: container_linux.go:265: s tarting container process caused "exec: \"/usr/bin/asset/bin/AssetUPnP\": stat / usr/bin/asset/bin/AssetUPnP: no such file or directory". : Empty continuation lines will become errors in a future release.
ASSET UPNP USER MANUAL INSTALL
RUN usermod -u 99 nobody & usermod -g 100 nobody & usermod -d /home nobody & chown -R nobody:users /home & apt-get update & apt-get install -y wget & mkdir -p /usr/bin/asset & chmod -R 777 /usr/bin/asset & cd /usr/bin/asset & wget & tar -zxvf *.gz & rm *.gz & apt-get purge -remove -y wget & apt-get autoremove -y & apt-get clean Unfortunately I get a warning when building: I try to built a docker from a raw dockerfile send to me by Sparklyballs.
0 kommentar(er)
