Introducing the “rhel-tools” for RHEL Atomic Host
developerblog.redhat.com
Introducing the “rhel-tools” for RHEL Atomic Host
1–10 of 18 posts
Re: Introducing the “rhel-tools” for RHEL Atomic Host
#2Maybe containers can be the norm for all systems. Not just specialized server OSes. Need to install a video editing suite that has many packages? - use the container, etc.
Re: Introducing the “rhel-tools” for RHEL Atomic Host
#3Maybe containers can be the norm for all systems. Not just specialized server OSes. Need to install a video editing suite that has many packages? - use the container, etc.
I can't help but think what a failure of the Linux user land this is - we're essentially saying the only thing we can count on being there is the kernel?
Re: Introducing the “rhel-tools” for RHEL Atomic Host
#4Maybe containers can be the norm for all systems. Not just specialized server OSes. Need to install a video editing suite that has many packages? - use the container, etc.
With systemd we are almost there http://www.freedesktop.org/software/systemd/man/systemd-nspa...
Re: Introducing the “rhel-tools” for RHEL Atomic Host
#5Maybe containers can be the norm for all systems. Not just specialized server OSes. Need to install a video editing suite that has many packages? - use the container, etc.
I can't help but think what a failure of the Linux user land this is - we're essentially saying the only thing we can count on being there is the kernel?
Despite the plethora of Docker articles here on HN, I haven't paid much attention to containers. Reading this article, I get the impression that they occupy a niche somewhere between a chroot jail and a VM.
The question is, how to deploy an application in this kind of environment? Maybe I build a minimal container and find that a DBMS works fine until it does something like dlopen("/usr/lib/libxml2.so"). Oops, rebuild the container with another library and try again.
After fixing one of the broken links in the blog post, I found this article, which describes an Oracle container:
http://rhelblog.redhat.com/2014/10/29/containerizing-databas...
Re: Introducing the “rhel-tools” for RHEL Atomic Host
#6Maybe containers can be the norm for all systems. Not just specialized server OSes. Need to install a video editing suite that has many packages? - use the container, etc.
I can't help but think what a failure of the Linux user land this is - we're essentially saying the only thing we can count on being there is the kernel?
There is no such thing as a linux user land. So no, the only thing you can count on is the kernel.
Re: Introducing the “rhel-tools” for RHEL Atomic Host
#7Maybe containers can be the norm for all systems. Not just specialized server OSes. Need to install a video editing suite that has many packages? - use the container, etc.
And when one of the usual system libraries is compromised (glibc, libssl, libxml), everyone need to update their containers.
To make this workable, I guess you have to union mount the application-specific filesystem over a filesystem with ABI-stable system libraries.
Re: Introducing the “rhel-tools” for RHEL Atomic Host
#8Earlier quoted context omitted.
I can't help but think what a failure of the Linux user land this is - we're essentially saying the only thing we can count on being there is the kernel?
Despite the plethora of Docker articles here on HN, I haven't paid much attention to containers. Reading this article, I get the impression that they occupy a niche somewhere between a chroot jail and a VM. The question is, how to deploy an application in this kind of environment? Maybe I build a minimal container and find that a DBMS works fine until it does something like dlopen("/usr/lib/libxml2.so"). Oops, rebuil…
Yeah, it's called testing. But it's no different from, say, building a server and finding that the DBMS works fine until it doesn't. The only difference is that when you fix it, you can be sure(er) that you've actually fixed it, compared to a classic server, where there is a lot of state that can obscure the real problem.
Re: Introducing the “rhel-tools” for RHEL Atomic Host
#9Earlier quoted context omitted.
I can't help but think what a failure of the Linux user land this is - we're essentially saying the only thing we can count on being there is the kernel?
Despite the plethora of Docker articles here on HN, I haven't paid much attention to containers. Reading this article, I get the impression that they occupy a niche somewhere between a chroot jail and a VM. The question is, how to deploy an application in this kind of environment? Maybe I build a minimal container and find that a DBMS works fine until it does something like dlopen("/usr/lib/libxml2.so"). Oops, rebuil…
Thank you, we will fix the link.
Re: Introducing the “rhel-tools” for RHEL Atomic Host
#10Maybe containers can be the norm for all systems. Not just specialized server OSes. Need to install a video editing suite that has many packages? - use the container, etc.
I see it as Red Hat's attempt to mitigate the long life cycles of its releases. Balancing the stability of a consistent OS without have to deal with an out of date (prehistoric) tool set.