I've looked it up and it appears that most changes to the kernel are 
channeled through http://www.kernel.org and distros get their kernel from 
them, BUT then they also modify it 
to tune it finely to their goals, and also use different configuration 
options when building their kernels, so as you well say, "yes broadly 
speaking" but there are code 
differences.   Perhaps they take care that those never conflict with 
userland dependencies so not much goes wrong.  

I think I am going to make sure that the userland base in containers is the 
same flavor of the docker host OS, just in case. 

Thank you for your reply, Dreamcat.

Joseph 




On Friday, August 19, 2016 at 3:05:06 AM UTC-4, Dreamcat Four wrote:
>
>
>
> On Fri, Aug 19, 2016 at 3:50 AM, Tiglath <tiglat...@gmail.com 
> <javascript:>> wrote:
>
>> Don't mean to abuse the privilege but this question nags me...
>>
>> If as you say the different Ubuntu, CentOS, etc, images from the repo 
>> have no kernel and only the userland libs and bins, and rely on the host 
>> kernel. Are kernels in all distros generic enough to work with any flavor 
>> of userlands?  
>>
>
> Yes broadly speaking that seems to be the case.
>
> Although I don't think I'm knowledgable enough to give you the best 
> answer. But also quite often these official docker base images are also 
> build specifically to work inside docker. And in that they may include any 
> necessary tweaks or work-arounds if they have their distro's kernel 
> modified to do specific non-standard things. Or simply omit / exclude a lot 
> of un-needed files that simply aren't applicable. As you are only running 
> some simple programs yourself in there.
>
> For example a distro's full init system / services dont need to be 
> started. Usually none of it is activated.
>
> Also there are quite a few kernel features which are given access or are 
> restricted though specific docker options. Some of which can be configured 
> on a per-container basis as docker run options. So then the distro userland 
> files really have nothing much to do with that aspect of operations.
>
>
>
>  
>
>>
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "docker-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to docker-dev+...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"docker-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to docker-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to