Slashdot Mirror
Red Hat Strips Down For Docker
angry tapir writes Reacting to the surging popularity of the Docker virtualization technology, Red Hat has customized a version of its Linux distribution to run Docker containers. The Red Hat Enterprise Linux 7 Atomic Host strips away all the utilities residing in the stock distribution of Red Hat Enterprise Linux (RHEL) that aren't needed to run Docker containers. Removing unneeded components saves on storage space, and reduces the time needed for updating and booting up. It also provides fewer potential entry points for attackers. (Product page is here.)
I know I know! They also took out the Linux kernel, leaving only systemd.
https://www.youtube.com/watch?...
I hope centos team will compile this version
Does systemd already have a poorly coded version of this installed?
Only the State obtains its revenue by coercion. - Murray Rothbard
Dockers
Discuss.
I've been using debian vservers in the past, and now lxc. RedHat 7 and its LXC integration is amazing. I use KVM as my hypervisor of choice, so I'm already using virtual machine manager, so now I can manage my LXC hosts with VMM, its really a nice touch.
What really interests me is LXD. LXC containers in a real isolated container that I can just move. Right now, I'm stuck to zipping and moving LXC's directories if I want to move them. I tend to use OS containers stripped down, because I want app/tcp/ssh/nrpe installed, so I can make sure the service is alarmed, and I use ssh for remote management.
Docker tends to be aimed at enterprise usage, if you have lots of single applications appliances, you can roll out and tear down, docker is a great idea.
That is a different use case, so I don't need docker, but docker is built on LXC, so I get that added benefits from support from Redhat. (and Centos7 support)
I'm running an IT shop, so my servers run for years, and I need to be able to manage, and support them. LXC containers is the perfect middle ground for me. LXD is the only thing I'm missing, moving file based containers.
So, I'm happy docker is pushing technology, because the stack it runs on is also benefiting from it.
BTW, I wish Redhat would support LXC VM's on its REHV (ovirt) platform, then I could consolidate even more VM's into single VM's. Guests with bridges with macs are filtered due to IP spoofing rules. Kinda silly when RedHat pushes LXC on 7, but doesn't test LXC on its Visualization platform.
This is the original DOCKER
This submission's comments are yet another superb example of how systemd is absolutely tearing apart the Linux community. Most of the comments are either anti-systemd, or they're somebody scolding somebody who is anti-systemd. And there's the comment linking to the picture of the guy with the cell phone stuck in his foreskin, but that's unrelated.
Any time that Linux is the topic of discussion here, or at numerous other sites, the same thing happens: people rightfully post about how bad systemd is, then some others come and cry about how people are rightfully pointing out how bad systemd is, and there is lots of disagreement.
Ten years ago, or five years ago, or even two years ago, I never would have believed that Red Hat of all companies would be responsible for causing so much disruption to the Linux ecosystem. Yet here we are. It isn't Microsoft causing this discontent. It isn't SCO. It isn't Apple. It's a creation of Red Hat that's single-handedly ruining everything that was great about Linux! Systemd is splitting the Linux community into several warring factions, and it's even driving some people over to the BSDs. It's unbelievable.
Did they strip it back down to a sane bare bones Unix?
not everyone knows Docker is yet another piece of cloud wankery
Juju is able to orchestrate both LXC and KVM on several different cloud environments. Juju employs a slightly different paradigm than Docker, building on top of cloud images rather than an image based workflow. It surprises me that Docker gets so much attention in this space. I have used both and still prefer Juju for the flexibility. With Juju I am able to nest LXC inside Amazon instances or use LXC on my laptop to make it appear as cloud environment.
A quick google search turns up a document on this very subject (not written by me):
https://insights.ubuntu.com/wp...
"Tempt not a desperate man" - Willy S.
They already bent over for systemd.
Tip one: be aggressive out of the gate and apply pressure point marketing. When a business is under new management it is a great time to snag new customers and to make Nike Tn Requin sure that your station and store become the chosen location for a host of new people. Think of some new ideas - for example, some large signs announcing a price reduction for a limited time, or a free cup of coffee served at the pumps during the first week. Establish your brand with uniformed and energetic employees giving out coupons or other incentives by every pump. Put the previous owner to shame after just one week of aggressive selling. Tip two: go out and look for new clients by copromoting with other merchants in your area. Tour the locality and see where people are shopping. For example, make a deal with the supermarket manager to distribute their coupons if they will reciprocate. Car washers or tire vendors are great places to co-promote. Be creative! Tip three: start talking with your vendors. Now is the time as a new owner to negotiate aggressively as you have the advantage. Everything in your store should be renegotiated, from coffee to snacks to magazines. Open the playing field by inviting other vendors to tender http://www.wsdyty.com/ .
I don't get it... what's the for? is it for the host running the containers, or for the containers themselves?
I set up a bit of Docker goodness at work because I needed to do some stuff in RHEL5, 6 and 7 sort of simultaneously. I found getting the base image of a RHEL system into a container to be annoyingly hard - first of all, you somehow have to know what all the bajillions of 'base' packages are that you're going to need. Then you make your container and spin it up to a bash prompt. Great - all looking good, right? Wrong. For any other packages you want to install you need an RPM repo, only Redhat give you a satellite - for which you need a client license. You'll need one of those for every container you ever create - that can't be right, can it?
Maybe I'm completely missing the Chosen Path here, but getting Dockers up and going in an enterprise setting seems remarkably fiddly. That said, being able to spin up a considerably smaller container would be very welcome. I'm not so sure having a stripped down host to run them on necessarily excites me all that much, but whatever it takes to get the bloat out of distributions is fine with me.