grumpybutfun

I am not trying to hurt LT nor it's users, quite the contrary. I am HUGE fan of unRAID and want it to be the best NAS product out there. My passion for it shows with all the work I have done, my documentation and my posts. I GREATLY appreciate your work and all that do and I hope you continue. What you have done part time in only a few weeks is nothing short of amazing along with very professional and polished looking. unRAID believes I should go create / play in my own sandbox, I happen to agree with them. I totally disagree. Docker is HUGE and most unRAID users are going to use it over anything I have done with Xen / KVM. Virtualization certainly has it's place but for most unRAID users, Docker is way to go. Slackware and root ram file system is what unRAID is going to stick with for the foreseeable future and thankfully with unRAID choosing to install / use Docker... It is a great solution and solves some of the issues in the current unRAID environment. Linux Dorks like me have come and gone and unRAID didn't miss a beat. However, it's the WebGUI guys (you included) that are most valuable / needed. It's one thing that I can make unRAID do X, Y and Z but without people like you... The average unRAID user doesn't have the experience / knowledge / comfort level to drop down to a Linux command line to be able to use those things I share / create effectively / easily. My parting advice to you (and needo)... It's VERY IMPORTANT that both of you go learn about Linux control groups and work with unRAID to implement that into what you both are doing. They provide a lot of very useful metrics, but they also help to ensure that each container gets its fair share of memory, CPU, disk I/O; and, more importantly, that a single container cannot bring the system down by exhausting one of those resources. Also, since Docker 1.0 just came out and a lot more people are now using it there will be A LOT of releases over several months. They have already released Docker 1.1.0 and 1.1.1 is about to be released. There are many bug fixes and new features that you and needo will want to take advantage of as this moves forward. In your case, they are constantly working on the Docker APIs and there will be many updates / changes / additions in the next few months. Assuming unRAID rolls out Betas and updates Docker to the latest stable release... With those, it will allow you to share / show even more and give us the ability to make Docker easier to support / manage in your WebGUI. You will see they added some things for stop / stop, a pause and sockets parameter. Thanks again for all that you and needo have done. I personally have used both of what you two have developed and learned a great deal about Docker in the process.

Yeah... I am not going to be able to do it. I use to contribute here (KVM, Xen, XenServer, running unRAID in KVM on openSUSE, PXE Server, etc.) but my contributions / input are no longer wanted here. I think I have a lot of to offer but unRAID sees it another way. I finally got around to attacking Docker (Grumpy Style) and I did it A LOT of things differently than how we are doing it here now. I'm sure unRAID thinks I have this wrong too. 1. Using the wrong image. 2. Using the wrong init script. 3. Looking at this from a container level only and not the bigger picture. 4. Not creating a platform / image / method for users to easily add / implement / manage change their Apps in Docker. When addressing the 4 areas above 1. I created a Master Development Image that users would use to create Apps. 2. Developers use the Developer Image (a Linux Novice following any App install guide on the web could do this)... They would put the config files / scripts / packages (if any) into separate folders for the Master Container Image (Not the Developer Image this is a separate Container Image and it's a lot smaller than the one we use now). 3. Selected a Rolling Release Distro that also has a port system (TONS of apps that even Ubuntu doesn't have without jumping through hoops) along with whatever is in your typical package manager. 3. Running a simple command will then use (data, config, etc.) and suck in everything that is needed when making a real small container for the apps plus all the monitoring stuff you will see at the bottom. 4. Integrates with github and all updates, versioning, script modifications, etc. all are updated with a simple command. 5. Want to create a Wordpress Container that works in unRAID with our "standard" unRAID Docker format... Use the dockerfile, one ini file (which we all can see / create / modify / update) and run the docker build command and bam! 6. We are not monitoring Apps... We are only monitoring Containers. Monitor Application in all your containers in one WebGUI tab: Then in another WebGUI tab you can see all your containers, monitor / see the status and even be alerted (with sound) that an App within each Container is not working. Below instead of Server it would be Sickbeard/Edge Couchpotato/Stable, etc. and for the Processes it would actually say what each one is... Sickbeard, SSH, Deluge, etc. Running 15 Apps in 15 Containers works sure but you can run many Apps in one / several containers if you want. With my system, it's a matter of dropping in an INI file (for each app) and it would build containers that you customize with as many apps as you want. Plus unRAID hasn't figured out or told you about control groups and how to customize memory, CPU, disk I/O throughput, Prioritization, etc. for your container(s). Yes, my ini file (which you can edit yourself) handles all of that. I bet it's the first time that 95% of you are hearing about this. I suspect you will want your Plex to be in it's own control group and your Apps to use different control groups. Anyway... I was told to leave since unRAID and I disagree when it comes to providing an end to end solution for NAS / HTPC / Media / Applications Server. They basically do "apt-get install docker" and leave the rest to us. I want an end to end solution (including Best of Breed Practices, maintaining Images, packages, INI files, containers, VMs, etc.). I will release a docker solution like enterprises do it (sexed up of course and all done through a WebGui) and many other things with "GrumpyRAID" coming out soon.

Did you try this: http://lime-technology.com/forum/index.php?topic=31297.0 ? I will create a badass PXE Server that uses Tiny Core Linux and a HTTP Server (faster than tftpboot) for Menus and isos / images. I will work on it tomorrow and post it for all of you to test. Perhaps gfjardim wouldn't mind creating a slick WebGUI for adding / removing images and configuring the PXE Menu. I can get it close but he will need to take it the last mile. NOTE: I am not going to support this long term so one of you will have to take it and own it.

LOL! Yes, but if you need Wine... Create a Windows VM. What command line / Web App Windows program could you possible run that doesn't have a Linux equivalent?

emhttp combines a lot of different things / programs / functions into one and the webserver is one of those. From what Tom has indicated, he is going to pull the webserver "portion" out of emhttp (leave the other functions there) and perhaps use a "better" more stable one like Sickbeard, Couchpotato, Webmin, etc. do.

I think so. I have been running the new GUI from day one also and I have done all kinds of things to unRAID without it failing. unRAID running in a VM on unRAID (hope that makes sense) and even "baking" unRAID in other Distros and torture testing it without it failing. I suspect it has to do with the various packages (and versions) that the plugins use.

Great Guide and great alternative solution.