No, Docker is not becoming red hat - specific. From a technical standpoint this announcement means two things:
1) Docker 0.7 will run on vanilla kernels out of the box. This means virtually all distros will be supported. It also means wider support for hosting providers which don't allow custom kernels (Google Compute Engine for example).
2) Future versions of Docker will optionally support some of the technology used by Red Hat - most prominently libvirt-lxc and selinux.
The more places you can use Docker, the more useful it is :) So we have no intention of locking it into a single distro or paas.
That seems like the most probable path, although I can't speak for the people making that contribution.
What I mean, regardless of how we actually implement, is having an elegant way to deploy containers in environments where the sysadmin relies on SELinux contexts and labels to implement security.
Comments
No, Docker is not becoming red hat - specific. From a technical standpoint this announcement means two things:
1) Docker 0.7 will run on vanilla kernels out of the box. This means virtually all distros will be supported. It also means wider support for hosting providers which don't allow custom kernels (Google Compute Engine for example).
2) Future versions of Docker will optionally support some of the technology used by Red Hat - most prominently libvirt-lxc and selinux.
The more places you can use Docker, the more useful it is :) So we have no intention of locking it into a single distro or paas.
I'm assuming by SELinux you mean the work ontop of SELinux for virtual machines and containers with libvirtd named sVirt[1]?
[1] https://fedoraproject.org/wiki/Features/SVirt_Mandatory_Acce...
That seems like the most probable path, although I can't speak for the people making that contribution.
What I mean, regardless of how we actually implement, is having an elegant way to deploy containers in environments where the sysadmin relies on SELinux contexts and labels to implement security.