How does glibc within a Docker image survive different container host kernels?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1















Docker containers share the kernel of the host, but they do include their own applications and libraries. Is it correct that glibc is one of these libraries?



If so, how come there is no problem of glibc being incompatible with whatever kernel version the actual container host runs?










share|improve this question






















  • Glibc and compatible kernel versions: unix.stackexchange.com/questions/9705/…

    – Mark Plotnick
    Jan 9 at 1:50















1















Docker containers share the kernel of the host, but they do include their own applications and libraries. Is it correct that glibc is one of these libraries?



If so, how come there is no problem of glibc being incompatible with whatever kernel version the actual container host runs?










share|improve this question






















  • Glibc and compatible kernel versions: unix.stackexchange.com/questions/9705/…

    – Mark Plotnick
    Jan 9 at 1:50













1












1








1








Docker containers share the kernel of the host, but they do include their own applications and libraries. Is it correct that glibc is one of these libraries?



If so, how come there is no problem of glibc being incompatible with whatever kernel version the actual container host runs?










share|improve this question














Docker containers share the kernel of the host, but they do include their own applications and libraries. Is it correct that glibc is one of these libraries?



If so, how come there is no problem of glibc being incompatible with whatever kernel version the actual container host runs?







docker glibc portability






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 8 at 21:10









OvervOverv

1084




1084












  • Glibc and compatible kernel versions: unix.stackexchange.com/questions/9705/…

    – Mark Plotnick
    Jan 9 at 1:50

















  • Glibc and compatible kernel versions: unix.stackexchange.com/questions/9705/…

    – Mark Plotnick
    Jan 9 at 1:50
















Glibc and compatible kernel versions: unix.stackexchange.com/questions/9705/…

– Mark Plotnick
Jan 9 at 1:50





Glibc and compatible kernel versions: unix.stackexchange.com/questions/9705/…

– Mark Plotnick
Jan 9 at 1:50










1 Answer
1






active

oldest

votes


















2














Linux kernel is rather binary compatible when considering apps. If you see an incompatibility, it is most likely caused by



a. CPU architecture mismatch (obviously unrelated to kernel version) or



b. Library issues. Apps typically depend on some libraries. If any of them is missing or incompatible, then the app will likely not work.



Sure, there are some APIs/ABIs in kernel that might change across versions., so kernel incompatibility might happen in theory. It just does not happen so often…



Kernel modules are a different story, level of compatibility across versions is AFAIK quite lower there. But you don't need a kernel module for glibc…






share|improve this answer
























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493330%2fhow-does-glibc-within-a-docker-image-survive-different-container-host-kernels%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    Linux kernel is rather binary compatible when considering apps. If you see an incompatibility, it is most likely caused by



    a. CPU architecture mismatch (obviously unrelated to kernel version) or



    b. Library issues. Apps typically depend on some libraries. If any of them is missing or incompatible, then the app will likely not work.



    Sure, there are some APIs/ABIs in kernel that might change across versions., so kernel incompatibility might happen in theory. It just does not happen so often…



    Kernel modules are a different story, level of compatibility across versions is AFAIK quite lower there. But you don't need a kernel module for glibc…






    share|improve this answer





























      2














      Linux kernel is rather binary compatible when considering apps. If you see an incompatibility, it is most likely caused by



      a. CPU architecture mismatch (obviously unrelated to kernel version) or



      b. Library issues. Apps typically depend on some libraries. If any of them is missing or incompatible, then the app will likely not work.



      Sure, there are some APIs/ABIs in kernel that might change across versions., so kernel incompatibility might happen in theory. It just does not happen so often…



      Kernel modules are a different story, level of compatibility across versions is AFAIK quite lower there. But you don't need a kernel module for glibc…






      share|improve this answer



























        2












        2








        2







        Linux kernel is rather binary compatible when considering apps. If you see an incompatibility, it is most likely caused by



        a. CPU architecture mismatch (obviously unrelated to kernel version) or



        b. Library issues. Apps typically depend on some libraries. If any of them is missing or incompatible, then the app will likely not work.



        Sure, there are some APIs/ABIs in kernel that might change across versions., so kernel incompatibility might happen in theory. It just does not happen so often…



        Kernel modules are a different story, level of compatibility across versions is AFAIK quite lower there. But you don't need a kernel module for glibc…






        share|improve this answer















        Linux kernel is rather binary compatible when considering apps. If you see an incompatibility, it is most likely caused by



        a. CPU architecture mismatch (obviously unrelated to kernel version) or



        b. Library issues. Apps typically depend on some libraries. If any of them is missing or incompatible, then the app will likely not work.



        Sure, there are some APIs/ABIs in kernel that might change across versions., so kernel incompatibility might happen in theory. It just does not happen so often…



        Kernel modules are a different story, level of compatibility across versions is AFAIK quite lower there. But you don't need a kernel module for glibc…







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jan 11 at 7:23

























        answered Jan 8 at 21:42









        v6akv6ak

        1916




        1916



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493330%2fhow-does-glibc-within-a-docker-image-survive-different-container-host-kernels%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown






            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay