How many Linux servers do I really need?
-
@DustinB3403 said:
Docker is meant to be running a bunch of identical processes side by side.
Hmmmmm..... I didn't know that. This course makes it seems like a container is a super lightweight VM.
-
@DustinB3403 I agree. Docker wasn't really meant for this. You can use it to do this, but it's very early stages currently. I give it another year before it even becomes useful for tinkering with in a lab.
In the mean time, most of those services don't require many resources at all. Depending on the hypervisor being used you may not be using more than a single kernel. My personal VPS is on that type of system, I can do anything with it but update the kernel, because the kernel is shared between all instances running on the server.
-
They are for all intensive purposes, but their supposed to be super targeted, with a very specific work-load. Which often needs to be run concurrently across a ton of discrete containers.
-
@anonymous said:
@DustinB3403 said:
Docker is meant to be running a bunch of identical processes side by side.
Hmmmmm..... I didn't know that. This course makes it seems like a container is a super lightweight VM.
Traditional containers are (LXC, OpenVZ, jails, zones) docker is a different animal.
-
@johnhooks said:
Traditional containers are (LXC, OpenVZ, jails, zones) docker is a different animal.
What one would be recommend in my use case?
-
@anonymous said:
@johnhooks said:
Traditional containers are (LXC, OpenVZ, jails, zones) docker is a different animal.
What one would be recommend in my use case?
If you're on Linux, I would recommend LXC. Ubuntu is making some interesting things with LXC and it's called LXD. One big feature is it will have live migration.
If you are on Solaris you would use zones, if you are on BSD you would use jails.
-
@anonymous My default is XenServer now that it's gone to a free to use, pay for support, model. Linux performance wise, it is among the best you'll find.
-
@johnhooks said:
If you're on Linux, I would recommend LXC. Ubuntu is making some interesting things with LXC and it's called LXD. One big feature is it will have live migration.
It's going to be Linux for sure. I am confused because this class has you to believe that Docker is better then LXC - there was a full 10 minute video comparing the two if I remember correctly. It seems that docker will some day support windows, where I don't think LXC ever will?
-
@anonymous said:
@johnhooks said:
If you're on Linux, I would recommend LXC. Ubuntu is making some interesting things with LXC and it's called LXD. One big feature is it will have live migration.
It's going to be Linux for sure. I am confused because this class has you to believe that Docker is better then LXC - there was a full 10 minute video comparing the two if I remember correctly. It seems that docker will some day support windows, where I don't think LXC ever will?
Wait, are they saying you can run Windows in a container or that you can run containers on Windows? I've heard something similar the latter, but not the former.
-
@johnhooks said:
Wait, are they saying you can run Windows in a container or that you can run containers on Windows? I've heard something similar the latter, but not the former.
Running containers on Windows. Run windows in a container would be nuts
-
LOL - I was wondering what benefit you'd get from running Windows inside a Linux container? (though I suppose one could say we already do that with XenServer - lol
-
@anonymous said:
What about if I use Docker?
Docker would be just as acceptable as LXC or separate VMs. Not likely a good choice as it is not designed for your needs, but it would work. Just be a lot more work.
-
maintaining all of these micro VMs seems like such a pain in the ass. But I'm guessing there are tools, or at least scripts that can be written that will take care of all of them at once?
-
@anonymous said:
@DustinB3403 said:
Docker doesn't add more to what you need, unless you want to go that route, and split the services with it... But virtualization would do this just as well in your case.
What about all the processing, memory, and space I save only having 1 OS?
It's trivial. For the same reasons that VDI is sometimes better than Terminal Servers - because the hypervisors do such an amazing job of this that the memory, disk, etc. does not expand like you would expect and the overhead of multiple VMs is very small. So small that unless you have a hugely saturated server, I can't imagine that you would notice. Containers are lighter than VMs, no doubt. But way more work and less flexible.
-
@anonymous said:
@DustinB3403 said:
Docker is meant to be running a bunch of identical processes side by side.
Hmmmmm..... I didn't know that. This course makes it seems like a container is a super lightweight VM.
Docker's purpose is to support extreme DevOps workflows where machines are never (literally, never) logged into and are built through tooling and in large numbers and never updated but destroyed and replaced instead. Can you do other things? Sure. Will it be fun? Heck no. Docker's design is around something so completely alien to the SMB market than the effort to use it well would be enormous.
-
@anonymous said:
@johnhooks said:
Traditional containers are (LXC, OpenVZ, jails, zones) docker is a different animal.
What one would be recommend in my use case?
LXC is the last traditional container technology on Linux. It ate OpenVZ. Docker and LXC completely own the market now. Rocket is an up and coming player. Jails requires FreeBSD. Zones requires Solaris.
-
@johnhooks said:
@anonymous said:
@johnhooks said:
If you're on Linux, I would recommend LXC. Ubuntu is making some interesting things with LXC and it's called LXD. One big feature is it will have live migration.
It's going to be Linux for sure. I am confused because this class has you to believe that Docker is better then LXC - there was a full 10 minute video comparing the two if I remember correctly. It seems that docker will some day support windows, where I don't think LXC ever will?
Wait, are they saying you can run Windows in a container or that you can run containers on Windows? I've heard something similar the latter, but not the former.
Microsoft is working hard to get Windows Containers ready because they've been left in the dust, again, and it is massively impacting their market.
-
@Dashrender said:
maintaining all of these micro VMs seems like such a pain in the ass. But I'm guessing there are tools, or at least scripts that can be written that will take care of all of them at once?
Yup, once you go DevOps containers are zero effort.
-
@Dashrender said:
LOL - I was wondering what benefit you'd get from running Windows inside a Linux container? (though I suppose one could say we already do that with XenServer - lol
Same benefits of containers anywhere. Lighter than virtualization.
-
@scottalanmiller said:
@anonymous said:
@DustinB3403 said:
Docker is meant to be running a bunch of identical processes side by side.
Hmmmmm..... I didn't know that. This course makes it seems like a container is a super lightweight VM.
Docker's purpose is to support extreme DevOps workflows where machines are never (literally, never) logged into and are built through tooling and in large numbers and never updated but destroyed and replaced instead. Can you do other things? Sure. Will it be fun? Heck no. Docker's design is around something so completely alien to the SMB market than the effort to use it well would be enormous.
With that being the case - then why do we hear so much about it? OK maybe not actually hear real information - but everywhere I turn - Docker docker docker docker docker this, docker that - and MS will support docker soon too - etc... it seems odd that even places like SpiceWorks at times seems overrun by it - is it simply that SMB IT personal don't want to be left in the dust so we glom onto anything we can?
Personally I felt like I missed the beginning of virtualization because to me it felt like it was for enterprise only - of course now it's being touted as the absolute starting point for any project unless you can show specific reasons why it doesn't/can't/won't work for your project (unlike SAN, which should still primarily live in the enterprise)
