Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Locked thread
NeoHentaiMaster
Jul 13, 2004
More well adjusted then you'd think.
Historically containers are basically the product of several kernel level features that provide both process isolation and resource management for one or more processes that have been grouped together. In essence a container is a "really fancy chroot" that is more analogous to virtual memory than traditionally understood virtual machines. Processes in a container usually have at least an additional layer of virtualizated memory, CPU priority, network devices and their own restricted view of the file system.

One of the biggest use cases for this were things like VPS products. Prior to time that hosting providers like AWS and Linode appeared, if you had any kind of dedicated server that didn't cost thousands a month your dedicated server was probably actually a container. Containers were far more popular with hosting providers mostly for economic reasons. You can oversell containers on a single physical server a lot more than you can hardware VMs. They are also a lot easier to manage and secure since it is impossible to be locked out of them. From the hosting providers point of view all the processes running on your server are just one of many groups of processes running on their servers operating system.

Now with Docker you have a platform that is using the same kind of underlying kernel features for process grouping and isolation, but instead of using them to make virtual servers they are used to make a very generalized application server with a bunch of user space tools for application deployment and management. I'm surprised I haven't head more parallels drawn to "Write once, run anywhere" promise of the JVM. Essentially Docker offers you the same thing but in any language. Once your app is packaged up as a docker container it can be deployed anywhere that is running docker and """should""" function identically.

Adbot
ADBOT LOVES YOU

NeoHentaiMaster
Jul 13, 2004
More well adjusted then you'd think.
Ansible is useful for remote command execution and orchestration. If you're using it as a configuration management framework for more than a dozen machines you are a FOOL.

NeoHentaiMaster
Jul 13, 2004
More well adjusted then you'd think.

pushing yaml files from arbitrary locations doesn't scale on both infrastructural and organizational levels.

  • Locked thread