Capt.Insano

Could anyone tell me what needs to be changed to made my virtual drive appear as a SATA drive instead of an IDE drive?? According to this blog post: http://www.blisshq.com/music-library-management-blog/2014/06/03/installing-vortexbox-kvm/ VortexBox expects the HDD to be located at /dev/sda (SATA) instead of /dev/hda (IDE) or the install fails. I need to set VirtualDrive to appear as a SATA drive I have tried to change "Disk dev name:" to sda instead of hda, but still no luck. Any ideas? Thanks!

Worked!! Setup bridge was set to no. Thank you very much!

I am brand new to KVM, previous user of VirtualBox and regular user of Docker. I have read all I could find in this subforum and on the wiki but only got myself confused; Let me begin!!: I have unRAID booted in normal (non-Xen) mode I have added the VM manager Plugin from here I HAVE seen the "No domains defined. Create from template or add XML." error at the bottom on the KVM page, googling it I got to https://lime-technology.com/wiki/index.php/UnRAID_Manual_6#Preconfigured_Templates but I cannot find any preconfigured templates to download as mentioned in the wiki so I continue... I have tried to set up a Virtual Machine as shown here: When I click Create VM, nothing happens. So what is a Domain xml etc.? also do I need to set up a network bridge? I am sure I have missed something really obvious but any help for a VM noob would be really helpful!!

Look under /unRaid in Tonido!

Look at the Tonido wiki or forums for multiuser instructions or Just run multiple Tonido containers on different ports to allow different users!!

Didn't have any excessive CPU use during indexing myself (and I also run Folding@Home full-time), but you could always look at the following to use CPU pinning: http://lime-technology.com/forum/index.php?topic=36257.0

Reserved

Released: http://lime-technology.com/forum/index.php?topic=39065.0 Hope ye enjoy! The Capt

Hi folks I have put together a container for Tonido server. It allows secure remote file management(including downloading files from unRAID server remotely) and file access (Video/Audio Streaming etc.). It also comes with some pretty great iOS and Android apps for remote access. Official Blurb: It is fairly self explanitory when set up. Go to: http://www.tonido.com/ for more info. To get it, just add my repo: https://github.com/CaptInsano/docker-containers/tree/templates Hope you enjoy, The Capt.

To confirm my own suspicion: Yes, yes usernames can be easily changed via the WebUI!! See screenshot attached!

Can't it also be done through the webui? I seem to remember changing it very easily through the webui.

I also use plop bootmanager, my server does actually support USB booting but only at USB 1.1 speeds for some weird reason so boot took FOREVER!! Now I have my server to autoboot to CD with plop on it, plop then loads proper USB drivers and boots off my unRAID USB stick WAY faster than without plop. Hopefully you can get this to work and get your test server up and running again, I find Docker great but I really want to try and run Vortexbox on my server and it need proper virtualisation. Anyway, best of luck!

I have a Tonido Container build and running on my unRAID server, I will post it next week. I tried to finish and post it today but github was under DDoS attack and my builds kept failing in the Docker registry. Keep watch for a post in the next week hopefully!! The Capt. P.S: Ignore the wrong icon in the first attached screengrab, I have no proper icon set in my test-template.xml

I'm also having trouble getting ddclient to work using namecheap as my host. Spent an hour on the livechat support with them and my .conf is good so would love a bit more info on this one. I currently have my /config mapped to /mnt/cache/appdata/ddclient If I start the ddclient with no conf it creates the sample one in my appdata/ddclient folder and I then edit it, and my log when I restart shows. *** Running /etc/my_init.d/firstrun.sh... Using existing config file. *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 9 Setting up watches. Watches established. So I assumed that meant it was using my conf file, but it would explain my problem if the above is correct. Unfortunately I can't work out how to navigate to /etc/init.d/ within the container to look and check. Got so far as docker ls but cannot work out how to browse the docker file system to check. I have also added this fix now. @smdion, great to see you still around the forums. After finding this bug in the DDClient container, I cloned you DDClient github,made some adjustment and put it in my repo. All credit was still given to you, see here for details and list of fixes: http://lime-technology.com/forum/index.php?topic=38146.0 If you want, have a look at the changes in my github here: https://github.com/CaptInsano/docker-containers/tree/master/DDClient and pull whatever ones you want into your own! Great to see you back, The Capt.

I have not been able to repeat any of those errors on a completely fresh install (all config files removed) both with EDGE=0 or EDGE=1. Is there anything special about your setup? Eg: Is /config mounted to non cache/array device eg. SNAP device ? Anyone else seeing these errors?

Do you have a file /config/certs/server.key? Check with other browser, clear your cache? Have you done a CLEAN install (remove all prev config)? I have never had any of those errors. It looks like git is failing due to a set fault and even mv is giving errors. Are you running docker in a standard btfs docker.IMG?

New build up ruTorrent directory was not being created for people with EDGE=0. Sorry for delay Please test and report.

For all with problems: Sorry about this. I think there must be a problem with the edge script. I think it is deleting the /config/rutorrent folder. Meaning that nginx has nothing to serve either on http or https. I will try and recreate the problem after work and look for a fix. Again, sorry about this.

@JaY_III & @Vaseer Did you set an EDGE variable (ie EDGE=1 or EDGE=0)? does your /config directory have a rutorrent subdirectory? I found a possible bug in the edge script, new version currently building; please report. (new build should be ready 10 mins from time of post now ready) also: SSL only works on https://xxx.xxx.xxx.xxx:8099 (not port 8089, https very important)

Keep me updated, I really hope the autotools file creation mask is sorted!!

Big Update I have made some major changes to how this container has been put together: The Container Template .xml has been updated to reflect the following changes (I would advise re-clicking "Save" under the "Docker Repositories" tab to ensure you have the latest template .xml) Changes 1. Updated to latest rTorrent (0.9.4) and libtorrent (0.13.4) 2. Added BASIC auth security: (.htaccess file is created in the /config folder) Default username:password is admin:admin To change this edit the .htaccess file, convert username:passwords into encrypted format here: http://www.htaccesstools.com/htpasswd-generator/ Follow the instructions; one username:password per line. Save file and Restart container 3. Added SSL (default https://SERVERIP:8099) This port can be changed in the Container settings The cert is created on container start and creates a generic server.crt in /config/certs All info in this generic cert is set to "unraid" If you want to swap out this cert with your own (advised) then: SSH into your unRAID server, navigate to the certs folder where you have mapped /config go to this link and follow instructions: http://www.akadia.com/services/ssh_test_certificate.html Make sure the output file is named server.crt Note: This can be done from unRAID itself not within the container Restart the container after replacing the server.crt 4. (Finally!!) Fixed umask of torrent user. umask torrent = 0002 I really hope people are happy with the changes and enjoy this container. The Capt.

Expect a new build tonight with SSL and Auth support (I will add an optional SSL=1 environmental flag for people not bothered with SSL) Auth username & password will be configurable through a file in the /config directory. I will look into this, it will mean building rTorrent within the container however which will increase the size of the container more than I would like. I am struggling to find a proper fix for this, I do not fully understand how to set mask settings for a user such that all files/directories created by the user "torrent" have 777 permissions. It is likely due to your firewall settings as I can download no problem. Check your settings however in .rtorrent.rc file in the /config folder. You can have encryption on or off. Thanks

I don't currently use any dockers so keep that FWIW. If I decide to go to dockers instead of my Ubuntu VM, I would prefer that ssl be default with authentication on rutorrent. Fair enough. Adding Basic Auth looks to be really easy (I have done it in my own container). But it will mean that Basic Auth will be active for everyone (Usernames and Passwords editable of course, through a .htpasswd file in /config) Defaulting to SSL looks more involved but I will look at it if people really want it. Poll added to OP. The Capt.

Query/Poll: Would most people prefer that this container defaulted to ssl (https) with some sort of authentication?

The newest build has the user torrent as a member of the users group, this should hopefully cause less permission problems. I just downloaded a torrent and AutoTools successfully moved it with no errors. If it is still causing issues, I may need some help from those more experiencesd than I!! This is something I will get to soon, even basic auth would be a great help here. leave it with me a while however as I am away this weekend. This is not a huge priority for me as then everyones ruTorrent docker would have multi-user enabled however, if you run docker exec -it ruTorrent /bin/bash you will be able to get "into" the container and make any changes you wish. (NOTE: changes will not be persistent over updates) Otherwise run multiple instances of the container as it is very lightweight. Further Update: I have changed the structure of the container so that the ruTorrent directory is in /config. This allows manually editing ruTorrent configs, adding 3rd Party ruTorrent plugins and ruTorrent configs are persistent across updates.