rjstott

No I switched to Krusader

I upgraded to 6.4.0 abd Dolphin no longer starts. I get the below error on the screen and the following in the log Sun Jan 28 09:41:25 2018 vncext: VNC extension running! vncext: Listening for VNC connections on port 5901 vncext: created VNC server for screen 0 error opening security policy file /etc/X11/xserver/SecurityPolicy Openbox-Message: Failed to open the display from the DISPLAY environment variable. Xvnc Free Edition 4.1.1 - built Nov 18 2014 16:07:18 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Underlying X server release 40300000, The XFree86 Project, Inc

Thankyou, the settings was just fine but deleting the file seems to have resulted in it having actually now gone. I have of course done this twice before and it didn't work and in the meantime I did clear up a lot of other lingering Docker files but heyho a good result.

I had terrible problems with all my dockers and part of the issue was that some of the files existed on both an array drive and the cache. I found the only way to get back to 'normal' was to delete all the support files in Appdata for Dockers on the array and the Cache then begin from scratch. You will lose all config data. It might be possible to copy some files elsewhere onto the array into a directory with a completely different name. This did work for me for everything I was worried about except Plex, where the support files are so numerous my server continually crashed. I still have a Docker.img file that exists on the cache and in the array that I can't fix. I also have a Mariadb database that I can't access but Nodered can. When copying make sure that you get the files you want as there may be two, one on the array and one on the cache.

Please find screenshot as requested

My system is a mess since upgrading to 6.4.0 as it forced a cache format. I have resolved a lot (and lost a lot) but the latest one defeats me. The Docker.img file is shown as on the Cache where it should be and on an array drive. This confuses me and confuses Mover. I have deleted the Docker.img file and rebuilt my Dockers but the problem has persisted. I see other reports with solutions that should have worked if I deleted and recreated the Docker.img file. The file I use is 60GBytes so please don't tell me its run out of space and because of the issue I have yet to rebuild most of my Dockers. Here is Mover log: Jan 26 00:09:02 Media root: mover: started Jan 26 00:09:02 Media root: move: file /mnt/disk3/apps/Docker/docker.img Jan 26 00:09:02 Media root: move_object: /mnt/disk3/apps/Docker/docker.img File exists Jan 26 00:09:02 Media root: move_object: /mnt/disk3/apps/Docker: Directory not empty Jan 26 00:09:02 Media root: move_object: /mnt/disk3/apps: Directory not empty Jan 26 00:09:02 Media root: mover: finished Did I miss a real fix that works? I lost Docker data because the backup files I created suffered a similar fate and it has been difficult to establish which files were in current use etc.

Hi, Just tried this and get an error as follows: "root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="FreePBX13" --net="bridge" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -p 8082:8082/tcp -p 5060:5060/tcp mima84/docker-freepbx Unable to find image 'mima84/docker-freepbx:latest' locally Pulling repository docker.io/mima84/docker-freepbx /usr/bin/docker: Network timed out while trying to connect to https://index.docker.io/v1/repositories/mima84/docker-freepbx/images. You may want to check your internet connection or if you are behind a proxy.. See '/usr/bin/docker run --help'. The command failed." Tried a second time and it has installed ok. Let's see what we can do! Thanks for the Docker, I'm sure there will be a lot of interest.

Hi, just tried to install this docker and get an error as follows: "root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="HADashboard" --net="" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -v "/mnt/cache/apps/Docker/apps/hadashboard/lib":"/lib":rw -v "/mnt/cache/apps/Docker/apps/hadashboard/dashboards":"/dashboards":rw -v "/mnt/cache/apps/Docker/apps/hadashboard/hapush":"/hapush/":rw -v "/mnt/cache/apps/Docker/apps/hadashboard/widgets":"/widgets":rw jcreynolds/docker-hadashboard 508f63bdcb2ded5c1559bf957751524e9a97f29a5e567110207db8395e3a426b docker: Error response from daemon: Container command not found or does not exist.." Am I missing something? The subdirectories have been created but they are all empty!

Squid, you are quite right, that solution would work fine for me. I'm sure your script works fine and I would have used it if it was incorporated into the 'built-in' list and the functionality wasn't so new. My posting was really a way of documenting the problem in case anyone else came across it (it fairly messes up the Plex database!). I guess I was also querying whether the original recommendation to put Dockers on the Cache was still good as without implementation of a solution there is possibly an issue. Finally, I wanted to see whether anyone else had experienced this problem. I ought to add that I had a security camera docker that filled the cache up too, so there are other apps that can cause a problem! Of course using some of the other new CA tools such as Backup etc will also help in this area. I think in my case I am going to go with a slight modification to your solution and that will be to create a transit media fileset where new media files are kept. This will allow me to vet the media (watch/listen) before running a batch archive to the unRaid storage. I have two other reasons for this, one is that I use 'shingled' drives where I believe write once may be advantageous and the second allows me to batch feed new media to a second storage system as an incremental backup.

I've had my Dockers on the cache since I first started using Dockers. The main use is for the Plex Server and keeping the Plex Metedata files, Indices etc on cache certainly speeds things up. However, I have a problem. My Plex installation probably now uses half of the 256GB SSD cache drive and on more than one occasion I have managed to fill the balance of the cache with Media files in transit. By which I mean Mover hasn't got around to cleaning up the cache. Whilst this isn't a problem for those files, I'm pretty certain it does cause problems for the Dockers which may face a situation where the cache is full. I did see there was a script to invoke the mover and that this could run using the CA User Scripts. However, this seems to be a very clumsy solution to a problem that is inherent in using the cache for Dockers. So I was wondering whether anyone else has encountered this issue, whether they have adopted the script solution or is there another more elegant way of resolving this. I guess one way would be to install another SSD which is only used for the Docker files in which case it would be easy to monitor use of the Docker storage. Or perhaps what would be a solution would be for 'cache only' files to be allowed to overflow onto the unRaid drives should the cache become full. In which case the Mover would then cleanup 'cache only' files when space became available on the cache? Any thoughts?

Hi, Many thanks, and yes you are right about posting, however as there are numerous error messages in the Plex startup log it is not always easy to know what is important and what isn't. I like lots of others suffer dreadfully when changes are made such that what we had stops working, the instructions for setting up no longer match reality and because it is so long since we actually set things up we are a bit blase about doing it. IMHO a missing / shouldn't cause so much grief and if it is so vital or obvious it should get better error reporting (perhaps you ommitted the / in the path definition). As a quick work around 'for example' I just tried to install the Plex server on my Mac. All went well BUT similarly the client refused to see the Media! The only thing that worked was to use 'Analyze' which I've never ever used before! Really appreciate the help

Hi, here is the data you asked for and a short commentary. 1) Add Docker without path to Media (attach 1) 2) Plex start up, some network errors, I think I can ignore? (attach 2). Plex runs with Metadata but no Media 3) Add path to Media (attach 3) 4) Click done and Docker command fails and orphans the image (attach 4) I understand the path process and although it has changed this surely right? The Media is in sub-folders below LP2015 which I can map in Plex Plex_Docker_install.txt Plex_Log.txt Add_path_result.txt

I just switched to this docker and I'm encountering some problems. 1) I don't see anywhere to tell Plex where my media is. Previously I created paths to each Plex Category but there doesn't seem to be anywhere to add even a single path by default although the instructions imply there is 2) So I add a simple Path config and the following error pops up - Says something about 'Invalid volume destination path: 'LP' mount path must be absolute.' but I use all I did was provide a name and use the path select process /mnt/user etc 3) Then the Docker disappears and I am left with an empty orphan image file needing deleting? 4) The default config file should be on the cache but it isn't so this needs correcting every install? 5) Adding the Media path after a start (which Plex does though no media files just metadata) kills the image as per 2) I did visit the Linuxserver.io forum where there are reports of others with problems. Just tried the needo version and get this same error 'Invalid volume destination path: 'LP' mount path must be absolute' Advice/help please

Me too: Oct 21 09:59:01 Media root: sh: /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php: No such file or directory

A bit of an update. I tried to re-format the cache drive, fell over the need to select only one pool device but eventually selected xfs and nothing happened. I did all the other bits of removing the cache, bringing the array back on line and selecting Format. It selects for about a second and resets. It certainly didn't format the drive. Anyway, reselected btfs and put the cache back. Eerything worked but in the process of copying files I've deleted a lot and created a bit of cache space. So no recurring log errors and we'll see how it goes. Bit odd that the Format didn't work, would I need to remove the drive and fromat it elsewhere? The Docker at 20GB will run Emby too, 'cos I have been there but it's no longer installed. I've also had other apps running with Emby so I doubt that was the problem.

No, I only have Plex, Filebot and Logitech Media Server dockers. The Docker file is 20GB. I've deleted and recreated this but the errors remain. To my mind the problem is with the SSD filesystem and no error indicates any other path, plus creating space on the SSD allowed the dockers to start. But, the problem does seem to be Docker related.

docker.img is in-use, cannot mount unRAID OS Version: Unraid: 6.2.0-rc4 Memory: 16 GB (max. installable capacity 32 GB) Network: eth0: 1000 Mb/s, full duplex, mtu 1500 Description: Docker will not start because img file is in use How to reproduce: Everytime I try to start the NAS or if I enable docker in the settings Expected results: Docker and Container will start Actual results: Nothing starts Other information:This error is just like that reported by KNEX666 against RC2. I had earlier problems with the Cache Drive reporting full (it wasn't). I temporarily made the docker system work by creating some space on the Cache Drive but messages as follows are still happening: Aug 25 15:51:45 Media shfs/user: share cache full Aug 25 15:51:45 Media shfs/user: share cache full Aug 25 15:51:45 Media shfs/user: share cache full Aug 25 15:51:45 Media shfs/user: share cache full Aug 25 15:51:45 Media shfs/user: share cache full Aug 25 15:51:45 Media shfs/user: share cache full Aug 25 15:51:45 Media shfs/user: share cache full Aug 25 15:51:45 Media shfs/user: share cache full The Cache is 256GB and sits at 37% according to STATS and I would say that is about right. I am currently deleting more files and copying the remainder to the main drives with a plan to run a diagnostic repair or reformat of the cache and then copy back. Is there some obvious thing I didn't do, I upgraded to RC4 from 6.1.9 about a week ago.

Thanks for the pointer. Changing this docker setting from Bridge to Host fixes both of my problems and now I just have to decide which devices I will use to generate the sound output! I have to say I do like the Raspberry Picore solution with an audio amp board addon. This gives both a player and airplay output solution. The Chromecast produces some video to show what is playing and I might go with this for my main in-house sound. The error message I reported is still there but an old post somewhere said this might be a red herring!

Logitech Media Player (Airplay and Chromecast Bridges) I have LMS happily working but want to integrate Airplay and Chromecast devices. The approprate LMS Plugins have been installed and appear to run but neither finds any device to bridge. I get the following errors "[16-08-14 15:20:28.0236] Slim::Networking::Async::Socket::UDP::mcast_add (48) Error: While adding multicast membership, UPnP may not work properly: Invalid argument" in the LMS docker log. This may or may not be relevant. Both plug-ins have an option to set the LMS IP address or auto-discover. Which IP address would I set, the internal 172... or the external 192... Can the plugins find the airplay and chromecast devices from the docker? I see someone else wanting airplay, had any success?

I did the update but I still have the Black Screen.

Well I updated and like those above my Blackscreen persists. Please, has anyone got the cure for this?

I tried the suggestion above, here is the logfile, it didn't help and the alternate browser gives the same black window! There are some errors in there but are they significant? Is this log what should be expected? The banner at the top of the Black window says connected to Crashplan but I somehow doubt I have that connection? Xvnc TigerVNC 1.6.0 - built Dec 24 2015 16:05:46 Copyright © 1999-2015 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Underlying X server release 11202000, The X.Org Foundation Sun Apr 10 00:18:43 2016 vncext: VNC extension running! Apr 10 00:18:43 Media syslog-ng[46]: syslog-ng starting up; version='3.5.3' vncext: Listening for VNC connections on all interface(s), port 4239 vncext: created VNC server for screen 0 Warning: could not find self.pem Using local websockify at /opt/novnc/utils/websockify/run Starting webserver and WebSockets proxy on port 4280 Openbox-Message: Unable to find a valid menu file "/var/lib/openbox/debian-menu.xml" Starting CrashPlan Desktop... Navigate to this URL: http://Media:4280/vnc.html?host=Media&port=4280 Press Ctrl-C to exit WARNING: no 'numpy' module, HyBi protocol will be slower Sun Apr 10 00:31:26 2016 Connections: accepted: 127.0.0.1::41542 SConnection: Client needs protocol version 3.8 Sun Apr 10 00:31:27 2016 SConnection: Client requests security type VncAuth(2) Sun Apr 10 00:31:35 2016 VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888 VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888 Sun Apr 10 00:32:19 2016 Connections: accepted: 127.0.0.1::41602 SConnection: Client needs protocol version 3.8 SConnection: Client requests security type VncAuth(2) Sun Apr 10 00:32:29 2016 VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888 VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888 Sun Apr 10 00:32:50 2016 Connections: closed: 127.0.0.1::41602 (Clean disconnection) EncodeManager: Framebuffer updates: 1 EncodeManager: Tight: EncodeManager: Solid: 1 rects, 786.432 kpixels EncodeManager: 16 B (1:196609 ratio) EncodeManager: Bitmap RLE: 1 rects, 160 pixels EncodeManager: 69 B (1:9.44928 ratio) EncodeManager: Total: 2 rects, 786.592 kpixels EncodeManager: 85 B (1:37016.4 ratio)

I can't get started with Crashplan. I'm running 6.1.9 and Crashplan installs ok but when I start it I get a black screen which say is is logged in but won't do anything. I did exacly the same installation on a friends 6.1.9 and it installed and let me create a login into Crashplan etc. I've downloaded the Docker a number of times, I've removed it and reset the Community entry nothing gets the VNC screen to access the Crashplan site. The only clue I have is that the Docker setup screen isn't the same as the one that worked, as it has additional Container Volume entries which seem redundant (i.e. one is named UNRAID?). Has anyone a clue?

Still playing with Homebridge on a Rasp PI but plugins are installed using 'npm' which is an incremental process on the pi (i.e. you add each plugin as you need it) but for a docker I guess a start script could scan a plugin directory and install all the plugins at start up time? Otherwise, there isn't a UI and other than a log file the setup should be easy, though try as I might I have never managed to get a docker working unless some kind sole creates the necessary and adds it into the 'community'.