ironicbadger

OK. I quit. Its too much.

What's the point in rebalancing? If we assume all drives have a limited lifespan (not a ridiculous assumption) all you're probably doing by moving data around is potentially increasing the wear and tear whilst reducing lifespan. It's a nice idea that I often wanted when I first started out but really it's not necessary at all...

Morning all, I am back, and I have a slice of humble pie on my desk in front of me! I was wrong, Docker is the future. Would you believe it if I said I'm now a DevOps Engineer for a living after my post last year stating how I thought Docker wasn't so great? Times change. Why am I back? Well, a few reasons. I've been experimenting with Ubuntu as my server OS (not my beloved Arch) and it's been going quite well to be honest except for one key area; drive pooling. Drive pooling has turned out to be a massive pain in the arse and I've utilised MHDDFS and AUFS, each with it's own idiosyncrasies and instabilities. Therefore, in search of a set it and forget it I'm coming back to my old friend unRAID. I'll buy a big SSD for my cache drive to offset the write performance differential and all will be fine! Onto my thrust for this thread. After being 'out of the game' for a year or so around these parts, what's new? I've had a good look at some of the hero features but it'd be great to see what you guys actually think are the best parts of v6 so far. What are the best bits? What are the worst bits? Any gotchas? I'll be building a brand new server from scratch by the end of the month using Docker for my plugins and no virtualisation (so you could perhaps leave KVM / Xen updates out if you liked). Anyway, nice to be back. Cheers!

Thanks for looking into this for me. I also posted an issue on github which the docker author responded too. Thanks to your response and his I've got an instance up and running.

Looks neat.

i'm looking at getting an app called smokeping working. but need some help understanding the docker file and how to actually configure this app. https://registry.hub.docker.com/u/dperson/smokeping/

Bought this laptop last year and am selling it now with over 2 years warranty remaining. It's in a great condition with only a couple of really tiny marks on the bottom of the machine. The screen is perfect as it the display housing and top case / keyboard area. Always kept clean and the battery has been cycled properly with care. I used to be an apple genius, so always take a special pride in my apple gear. The auction includes: - 13 retina MacBook Pro with 256gb SSD and 8GB RAM - 2 years of AppleCare hardware warranty remaining - original genuine charger - OS X 10.10 pre-installed (if you want) - original box with all accessories Serial number is noted prior to shipping. Shipping is £10 with City Link 24hr service. Fully tracked and insured. More images: http://www.ebay.co.uk/itm/MacBook-Pro-13-3-Retina-8GB-RAM-256gb-SSD-2-4Ghz-i5-Late-2013-/271614713086? https://www.dropbox.com/photos/album/kMj2QgvlqP7u8IA

I went back to a dedicated gaming rig too. As you insinuate, its just a bit too fragile for even home usage.

Chromecast. Oh that might not work too well if you don't have a tablet or smartphone though.

Good evening all, I am writing this post with a view toward winding up my active involvement in the maintenance of the Xen / KVM / repo images and projects I've been running since January. There are numerous reason for this, some of them personal which I won't bore you with but others are more publishable. With the roadmap published by Limetech this week it is quite clear to me that headless Linux VMs, such my ArchVM, are not long for this world. Docker is the future for LT it seems, I'm not fully convinced yet but maybe I'll be proven wrong. Also, with the talk of potentially dropping Xen and the flip flopping over support various hypervisors I've decided to just call it quits as it takes up too much of my time to keep up with all the changes. I'm in the middle of writing a dissertation and am therefore a little pushed for time. Lately, and by that I mean the last 3-4 months, donations have all but dried up (bar the odd generous $5 here and there, thank you to those who did donate) yet my bandwidth usage is getting higher and higher, it approached 300gb last month. This is not sustainable or fair. As previously mentioned I am an MSc student and here in the UK we get no funding from the government so have to pay our own way and the few ££ a month matter. I'm also just a little bored of what unRAID has to offer. It is rather behind the times, admittedly better lately, but I'm seeing much, much better performance with AUFS and SnapRAID on a proper Linux distro base OS (not this Slackware crap). I enjoy being able to type 'package-manger install package' far more than what unRAID has to offer. I've been an unRAID user for 3+ years and know so much more now than I did when I setup my unRAID system, so if you like my training wheels are coming off. So in summary, I'm not going away or deleting my account or posts or anything but I will with immediate effect stop maintaining my ArchVM images (both Xen and KVM) and the ArchVMrepo. With that said, I use the archVMrepo for friends and family so you may get lucky and piggy back of that for a while but it will go away one day. I wish LT all the best and all that. Ciao for now.

Good evening all, I am writing this post with a view toward winding up my active involvement in the maintenance of the Xen / KVM / repo images and projects I've been running since January. There are numerous reason for this, some of them personal which I won't bore you with but others are more publishable. With the roadmap published by Limetech this week it is quite clear to me that headless Linux VMs, such my ArchVM, are not long for this world. Docker is the future for LT it seems, I'm not fully convinced yet but maybe I'll be proven wrong. Also, with the talk of potentially dropping Xen and the flip flopping over support various hypervisors I've decided to just call it quits as it takes up too much of my time to keep up with all the changes. I'm in the middle of writing a dissertation and am therefore a little pushed for time. Lately, and by that I mean the last 3-4 months, donations have all but dried up (bar the odd generous $5 here and there, thank you to those who did donate) yet my bandwidth usage is getting higher and higher, it approached 300gb last month. This is not sustainable or fair. As previously mentioned I am an MSc student and here in the UK we get no funding from the government so have to pay our own way and the few ££ a month matter. I'm also just a little bored of what unRAID has to offer. It is rather behind the times, admittedly better lately, but I'm seeing much, much better performance with AUFS and SnapRAID on a proper Linux distro base OS (not this Slackware crap). I enjoy being able to type 'package-manger install package' far more than what unRAID has to offer. I've been an unRAID user for 3+ years and know so much more now than I did when I setup my unRAID system, so if you like my training wheels are coming off. So in summary, I'm not going away or deleting my account or posts or anything but I will with immediate effect stop maintaining my ArchVM images (both Xen and KVM) and the ArchVMrepo. With that said, I use the archVMrepo for friends and family so you may get lucky and piggy back of that for a while but it will go away one day. I wish LT all the best and all that. Ciao for now.

Good evening all, I am writing this post with a view toward winding up my active involvement in the maintenance of the Xen / KVM / repo images and projects I've been running since January. There are numerous reason for this, some of them personal which I won't bore you with but others are more publishable. With the roadmap published by Limetech this week it is quite clear to me that headless Linux VMs, such my ArchVM, are not long for this world. Docker is the future for LT it seems, I'm not fully convinced yet but maybe I'll be proven wrong. Also, with the talk of potentially dropping Xen and the flip flopping over support various hypervisors I've decided to just call it quits as it takes up too much of my time to keep up with all the changes. I'm in the middle of writing a dissertation and am therefore a little pushed for time. Lately, and by that I mean the last 3-4 months, donations have all but dried up (bar the odd generous $5 here and there, thank you to those who did donate) yet my bandwidth usage is getting higher and higher, it approached 300gb last month. This is not sustainable or fair. As previously mentioned I am an MSc student and here in the UK we get no funding from the government so have to pay our own way and the few ££ a month matter. I'm also just a little bored of what unRAID has to offer. It is rather behind the times, admittedly better lately, but I'm seeing much, much better performance with AUFS and SnapRAID on a proper Linux distro base OS (not this Slackware crap). I enjoy being able to type 'package-manger install package' far more than what unRAID has to offer. I've been an unRAID user for 3+ years and know so much more now than I did when I setup my unRAID system, so if you like my training wheels are coming off. So in summary, I'm not going away or deleting my account or posts or anything but I will with immediate effect stop maintaining my ArchVM images (both Xen and KVM) and the ArchVMrepo. With that said, I use the archVMrepo for friends and family so you may get lucky and piggy back of that for a while but it will go away one day. I wish LT all the best and all that. Ciao for now.

Good evening all, I am writing this post with a view toward winding up my active involvement in the maintenance of the Xen / KVM / repo images and projects I've been running since January. There are numerous reason for this, some of them personal which I won't bore you with but others are more publishable. With the roadmap published by Limetech this week it is quite clear to me that headless Linux VMs, such my ArchVM, are not long for this world. Docker is the future for LT it seems, I'm not fully convinced yet but maybe I'll be proven wrong. Also, with the talk of potentially dropping Xen and the flip flopping over support various hypervisors I've decided to just call it quits as it takes up too much of my time to keep up with all the changes. I'm in the middle of writing a dissertation and am therefore a little pushed for time. Lately, and by that I mean the last 3-4 months, donations have all but dried up (bar the odd generous $5 here and there, thank you to those who did donate) yet my bandwidth usage is getting higher and higher, it approached 300gb last month. This is not sustainable or fair. As previously mentioned I am an MSc student and here in the UK we get no funding from the government so have to pay our own way and the few ££ a month matter. I'm also just a little bored of what unRAID has to offer. It is rather behind the times, admittedly better lately, but I'm seeing much, much better performance with AUFS and SnapRAID on a proper Linux distro base OS (not this Slackware crap). I enjoy being able to type 'package-manger install package' far more than what unRAID has to offer. I've been an unRAID user for 3+ years and know so much more now than I did when I setup my unRAID system, so if you like my training wheels are coming off. So in summary, I'm not going away or deleting my account or posts or anything but I will with immediate effect stop maintaining my ArchVM images (both Xen and KVM) and the ArchVMrepo. With that said, I use the archVMrepo for friends and family so you may get lucky and piggy back of that for a while but it will go away one day. I wish LT all the best and all that. Ciao for now.

Oh OK then, my fault. Obviously.

C'mon, read the first posts it's all there. Also, pfsense isn't a package it's an entire OS.

I bought some last year and rather pleased with them 8 months on. Review here http://blog.ktz.me/?p=145

Something like this... http://blogs.technet.com/b/haroldwong/archive/2012/08/18/how-to-create-windows-8-vhd-for-boot-to-vhd-using-simple-easy-to-follow-steps.aspx

a little. but there's no harm in making a list or documenting a set of known good with unraids implementation of docker. Sent from my Nexus 5 using Tapatalk

Cheers G. The reason most people wanted a larger image was for their Plex library. As you say, just use virtfs 9p and put the library directly on the cache drive (or array as you see fit).

I'm starting this thread as I believe we need to develop some form of an unRAID community Docker container tracker. Having tried out and gotten Docker working myself for the first time today I'm totally blown away with it's potential for headless apps that I run alongside unRAID, it's a real game changer and makes Linux headless VMs almost redundant for all but the most complex tasks. I've still got plenty of understanding left to bridge but it's all good practice for some rainy day when I'll need the knowledge. The tech has only been in unRAID a week and already it's becoming confusing to keep track of who has released what. Also a very short and concise Docker guide needs to be posted, I'm happy to do this but tbh I don't think I know enough to write it - any volunteers? The containers repository (or unRAID Docker hub if you like) needs to happen very quickly to prevent duplication. What do we think to making a separate dedicated Docker sub-forum which is locked until an admin approves you can post in it. This would house one thread per container as well as a master thread (updated by mods) with the 'known good' community container images. We can easily devise a standard post #1 format to make it easier to read for people choosing. I'll happily sort this out with LT if you guys think it's the way forward.

Yes absolutely. This definitely needs some organisation from LT.

How'd you do that then? You can see from my edit above the lengthy docker run command I'm issuing everytime.

Ok thanks, that seems to be working just fine with the --net="host" stuff. Any idea why when I restart the container it looses any and all changes made during the last 'run' of the container? EDIT: Answered my own question, I need to commit the changes to the docker image otherwise it just creates a new container based off the old image when I issue the 'run' command. Next Q, how do I set (on a per container basis) that changes are committed when stopping a container? EDIT2: Answered my own question again. Rather than storing any information in the container at all (be it a database, conf file or whatever) you should actually store this in unRAID and then 'passthrough' that directory to the container using -v flag in the run command. docker run -p 8888:8888 -p 55555:55555 -v /mnt/cache/btsync-docker/:/btsync/ -v /mnt/user/Media/:/mnt/unraid/ --net="host" -d btsync In the above docker run command note the two -v flags. The first is where I store the docker .conf files and sync data and then pass that through to the container and it appears in the containers filesystem under /btsync. The second is passing my array through which appears under /mnt/unraid. This docker stuff is pretty neat I have to say. Headless Linux VMs are done.

Hi all, I'm putting some hours into understand Docker today and have set my sights on getting a BitTorrent Sync docker container actually working. I have built a container successfully which is now running but there is one piece of my understanding which does not yet compute. Networking. root@unRAID:/mnt/cache# docker run -p 8888:8888 -p 55555:55555 -v /mnt/cache/btsync-docker/:/btsync/ btsync By using this application, you agree to our Privacy Policy and Terms. http://www.bittorrent.com/legal/privacy http://www.bittorrent.com/legal/terms-of-use total physical memory 536870912 max disk cache 2097152 Using IP address 172.17.0.3 UPnP: Could not map UPnP Port on this pass, retrying. UPnP: Could not map UPnP Port on this pass, retrying. UPnP: Could not map UPnP Port on this pass, retrying. UPnP: Unable to map port 172.17.0.3:55555 with UPnP. In virtualisation I just have a br0 that I connect via, but how does it work in Docker? 172.x.x.x isn't right surely? Ideas, help, explanation welcomed please. I'll post a working Dockerfile at the end of this when it's all working.

Some people are never happy. When I released it at 15GB people moaned it wasn't enough. 50GB and it's too big. Ugh. I'll upload another version later perhaps that is smaller.