spants

This is where I will be hosting some dockers that I find useful, built on a Phusion or Linuxserver base. Add to your templates if you wish. https://github.com/spants/unraidtemplates/ *** Also added template support for the official NodeRed docker image - loads the latest version!!!. You can extra nodes through the Palette menu option. Therefore I will retire my unofficial version. Make a copy of your appdata directory and rename any 'flow' files to 'flows' *** NodeRed ====== This is THE Internet of Things package!. See http://www.nodered.org and http://flows.nodered.org for more info. I use this to link with my TADO heating system, Ciseco wireless sensors and Open weathermap linked with EmonCMS to produce heating graphs. It uses building blocks to manipulate data from devices/databases/twitter/http/mqtt etc etc - very powerful! MQTT *** Revert to Mosquitto 1.4.8 and Alpine Linux 3.3 27th Jan 2020 - due to timeout bug found *** ==== Please see Skylord123's excellent tutorial on setting this up https://skylar.tech/installing-mqtt-under-docker/ Setup for port 1883 and websockets on Port 9001. Supports usernames/passwords and certificates. To add authenticated users to MQTT, create a file named passwords.txt and save in the config directory. On restart, these will be encrypted and added to the top of the passwords.mqtt file. You might need to run NEWPERMS to edit the config file. Dashing *** Updated 08-Dec-2015, added dev tools *** ====================================== From dashing.io = Dashing is a Sinatra based framework that lets you build beautiful dashboards. Key features: Use premade widgets, or fully create your own with scss, html, and coffeescript. Widgets harness the power of data bindings to keep things DRY and simple. Powered by batman.js. Use the API to push data to your dashboards, or make use of a simple ruby DSL for fetching data. Drag & Drop interface for re-arranging your widgets. Host your dashboards on Heroku in less than 30 seconds. This project was created at Shopify for displaying custom dashboards on TVs around the office. Sample dashboards installed at IPaddress:3030/sample and IPaddress:3030/sampletv couchDB ======= unRaid template for the (semi)official Apache couchDB docker https://github.com/apache/couchdb-docker

woohoo! Thanks! BTW, what triggers the update available message for a docker in unraid?. Is it the docker push to docker hub or do I change something on the xml/github? thanks Tony

Thanks - I have the repo name sorted out now. It is the name of the directory. Not sure of the icon not showing as they dont download for me. Anyone want to try my template? It installs NodeRed (nodered.org) on port 1880. Map /data to your where the flows will be saved. I will tidy it up after the cup final (come on Chelsea!) by adding some extra modules and description. https://github.com/spants/unraidtemplates/

Thanks - the repo name is the directory! Just need to sort out the icons not showing now...

I have built a template for Nodered and everything is working well. I have setup DockerHub and Github but I have the following issues: 1) the Template shows in the list as [nodered] nodered and I would like it to shown as [spants] nodered - where is the title of the repo defined?. 2) The icons do not work: In the template I defined: <Banner>http://i.imgur.com/zXpacAF.png</Banner> <Icon>http://i.imgur.com/zXpacAF.png</Icon> but these do not download... This is shown as a missing picture with url http://192.168.1.22/state/plugins/dynamix.docker.manager/images/spants-nodered-latest-icon.png Any ideas? Tony my unfinished template : <?xml version="1.0" encoding="utf-8"?> <Container> <Name>NodeRed</Name> <Description> NodeRed description here.[br][br] NodeRed will run on port 1880.[br][br] [b][span style='color: #E80000;']Directions:[/span][/b][br] [b]/data[/b] : in this path, Node Red will store it's configuration files. </Description> <Registry>https://registry.hub.docker.com/u/spants/nodered/</Registry> <GitHub>https://github.com/spants/unraidtemplates</GitHub> <Repository>spants/nodered</Repository> <BindTime>true</BindTime> <Privileged>false</Privileged> <Environment/> <Networking> <Mode>bridge</Mode> <Publish> <Port> <HostPort>1880</HostPort> <ContainerPort>1880</ContainerPort> <Protocol>tcp</Protocol> </Port> </Publish> </Networking> <Data> <Volume> <HostDir>/mnt/disk9/docker/appdata/nodered</HostDir> <ContainerDir>/data</ContainerDir> <Mode>rw</Mode> </Volume> </Data> <WebUI>http://[iP]:[PORT:1880]</WebUI> <Banner>http://i.imgur.com/zXpacAF.png</Banner> <Icon>http://i.imgur.com/zXpacAF.png</Icon> </Container>

This works really well... See my write up. http://lime-technology.com/forum/index.php?topic=35805.0

Thanks Guys Found that Crashplan on the server had bound itself to the vpn docker rather than my LAN. The settings limit the transfer rate of a WAN hence the slow speed!. Thanks for the confirmation that Docker is working correctly, it helped me solve the problem. Btw, I'm seeing 120Mbps - 168Mbps now from unraid to OSX encrypted usb 3 drive over 1Gb network. Much better!

Hi It might get lost in the other thread, but has anyone checked the restore speed from a crashplan docker? I have 100gb of data to restore locally and it is giving an estimate of 32 days! I would appreciate it if someone just try restoring a directory (to a different test path) to see if this is a docker/crashplan issue. thnx Tony

... as I said above, this requires many steps and is not a docker template format in it's current guise. You need to follow the instructions on github to install

Anyone tried a restore yet? I have a 100GB directory to restore and it is running at 300Kbps and estimating 31days!. I have a fully functioning 1000Mbs network card and other operations are really fast. The system has 16GB ram... Wondering if going back to the plugin would speed it up. ** SOLVED ** Crashplan docker was using the ip address of my vpn docker hence using the WAN profile.

This may have to installed manually following the steps in the post as there are a number of stages to follow...

Is there a way to list the base image version for each docker on the Docker tab? I have some templated Dockers that I update, but some manual ones too - it would be great to see what they are all based on, on the Docker list.

Good points!. I ran out of space early on and deleted all my dockers and recreated on a larger IMG files. It might be useful to add the /dev/loop8 size/free info to the Docker Tab so that we can keep an eye on it....

I have had a problem with the UI crashing and restarting has no effect. The only way to cure it (for me) is to delete the dynamix.cfg file on the boot/config/plugins/dynamix directory

I had a problem with plex (using v6 and docker) which was resolved by turning off cachedirs.... Another time it was my Headphones plugin on v5 causing stuttering.

Currently running on my raspberry pi but is slight underpowered (and a waste of a Pi!). I use an OBIHAI 110 and freepbx to do caller identification (International calls, "Windows Tech support", withheld numbers have to type in a number to continue). http://www.liquidstate.net/blocking-silent-and-nuisance-calls-with-an-obi110-raspbx-asterisk-pbx/ http://www.freepbx.org/

to set a watch (blackhole) directory: 1) stop the docker container 2) set the perms of the transmission directory (use newperms: I think there is a way of running transmission as user:nobody but I havent got that working) 3) edit settings.json and add near the end of the file: "watch-dir": "/complete/blackhole", "watch-dir-enabled": true **** make sure that you add a comma to the previous end of line if there isn't one there! **** 4) Create a blackhole in the complete folder 5) restart docker container 6) run the pipework command again... If you wanted a completely different directory not related to complete or incomplete, do the following: add this to the docker run commandline: (for example) = -v /mnt/disk9/blackhole:/blackhole:rw docker run -d --cap-add=NET_ADMIN --net=none -v /mnt/disk9/docker/appdata/transmission:/config:rw -v /mnt/user/downloads/torrents/incomplete:/incomplete:rw -v /mnt/user/downloads/torrents:/complete:rw -v /mnt/disk9/blackhole:/blackhole:rw --name transmission_run transmission and then use /blackhole as the watch directory in the settings file. Hope that helps!

sounds like openvpn not starting... if you used the appdata directory as per my version, stop the docker and look at the files in openvpn directory. pia_client_id should be 32 chars generated earlier pia.cred should have username and password on separate lines You should also have pia.crt and pia_ca_north.conf in there as well. You can just restart the docker to use changes. Also try a newperms on the appdata directory for this app...

I have managed to get this working and these are my quick notes. download zip from https://github.com/firecat53/dockerfiles and extract Transmission directory rename private_example directory to example edit example/pia.cred to add username and password create a pia_client_id by using the following command: head -n 100 /dev/urandom | md5sum | tr -d " -" edit config.ini change username and password for transmission edit Dockerfile (optional) change the following to use fusion as a base docker: FROM ubuntu:trusty to FROM phusion/baseimage:0.9.11 BUILDING the docker: Type: docker build -rm -t transmission . when done: docker run -d --cap-add=NET_ADMIN --net=none -v /mnt/disk9/docker/appdata/transmission:/config:rw -v /mnt/user/downloads/torrents/incomplete:/incomplete:rw -v /mnt/user/downloads/torrents:/complete:rw --name transmission_run transmission This differs to the commands the author gave as I wanted to link to my appdata and torrent directories on the unraid server rather than a volume. It wont work until you setup pipework: Unzip pipework to /boot/config and chmod +X to make it an executable then use /boot/config/pipework br0 transmission_run 192.168.1.39/[email protected] *** I had permission problems with the config files. If it doesnt work (it actually takes a while -1min- to load because the vpn has to be set up, then stop the docker and do a newperms on the data directory (mine is /mnt/disk9/docker/appdata/transmission). Restart docker and pipework *** You can set the docker to autostart and also add this to your GO file: sleep 120; /boot/config/pipework br0 transmission_run 192.168.1.39/[email protected] (I set the docker to 192.168.1.39 and my gateway is 192.168.1.1 = yours will be different) Let me know how you get on

Not my work.... but this works very well and started first time! https://github.com/kylemanna/docker-openvpn

Recently had the same problem and couldnt see a guide to expand the docker.image. I stopped containers, stopped docker, deleted the docker image and rebuilt with more space. As most of my dockers were my-templates - it was easy to rebuild as the data was stored outside of the docker.image.

Hi I have had a look at this. This is my clunky way of getting it working: 1) download the Dockerfile and 10-cgi.conf files to a directory on your unraid server 2) I edited my Dockerfile to use Phusion to save a docker base download #FROM ubuntu:trusty FROM phusion/baseimage:0.9.11 3) build the docker: (dont forget the trailing DOT!) docker build --tag="smokeping” . 4) start the smokeping docker: (this has my settings, yours will differ) docker run -d --name smokeping -p 8100:80 -v /etc/localtime:/etc/localtime:ro smokeping 5) The webinterface is now here: http://192.168.1.22:8100/smokeping/smokeping.cgi (this is my setup, your ip/port may differ) Advanced: docker run -d --name smokeping -p 8100:80 -v /etc/localtime:/etc/localtime:ro -v /mnt/disk9/docker/appdata/smokeping:/etc/smokeping:ro smokeping This allows you to store configs in /mnt/disk9/docker/appdata/smokeping The readme on github shows how to get the running config into this directory Hope that helps! Tony

Heres how I did it for Node-Red and BTSYNC create a directory and save the Dockerfile in it In that directory (eg for Node-red) docker build --tag="nodered” . docker run -d --name nodered -p 1880:1880 -v /etc/localtime:/etc/localtime:ro -v /mnt/disk9/appdata/nodered:/config:rw nodered Do not forget the DOT at the end of the first line!!!. There may be extra files to download as well as the Dockerfile - save them in the same directory. I think that you can do a pull from Github but Unraid didn't have the necessary files to do it (and I didnt know how to install them) See here for the post http://lime-technology.com/forum/index.php?topic=34846.msg323940#msg323940

Docker image installed on an array drive (btrfs - the others are reiser) with 7 dockers running... I used the following layout: disk9/docker/docker.img disk9/docker/appdata/directories here.... All fine so far!

http://blog.definedcodehosting.com/osx-qemu-kvm Thought that some folks might be interested... (there is also a followup with Yosemite)