default user not added to docker group, have to do su $USER?











up vote
0
down vote

favorite












I have Ubuntu 18.04. and after installing docker i added my user to docker group with the command 



sudo usermod -aG docker ${USER}


and logged in



su - ${USER}


and if I check id, my user is added to docker group.



But when I reopen the terminal i cant do docker commands without sudo unless i explicitly do su ${USER}



also, I can't find docker group with the default user.
What am I missing here?






linux docker







share|improve this question


















  • 2




    only do a restart.
    – gopy
    2 days ago






  • 4




    Changes to group credentials don't affect your current session. You just need to log out and log back in; it's not necessary to restart.
    – larsks
    2 days ago






  • 1




    yup! Thanks, it worked. Log out and log in. P.S. why is it necessary?
    – Sam
    2 days ago

















up vote
0
down vote

favorite












I have Ubuntu 18.04. and after installing docker i added my user to docker group with the command 



sudo usermod -aG docker ${USER}


and logged in



su - ${USER}


and if I check id, my user is added to docker group.



But when I reopen the terminal i cant do docker commands without sudo unless i explicitly do su ${USER}



also, I can't find docker group with the default user.
What am I missing here?






linux docker







share|improve this question


















  • 2




    only do a restart.
    – gopy
    2 days ago






  • 4




    Changes to group credentials don't affect your current session. You just need to log out and log back in; it's not necessary to restart.
    – larsks
    2 days ago






  • 1




    yup! Thanks, it worked. Log out and log in. P.S. why is it necessary?
    – Sam
    2 days ago















up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have Ubuntu 18.04. and after installing docker i added my user to docker group with the command 



sudo usermod -aG docker ${USER}


and logged in



su - ${USER}


and if I check id, my user is added to docker group.



But when I reopen the terminal i cant do docker commands without sudo unless i explicitly do su ${USER}



also, I can't find docker group with the default user.
What am I missing here?






linux docker







share|improve this question













I have Ubuntu 18.04. and after installing docker i added my user to docker group with the command 



sudo usermod -aG docker ${USER}


and logged in



su - ${USER}


and if I check id, my user is added to docker group.



But when I reopen the terminal i cant do docker commands without sudo unless i explicitly do su ${USER}



also, I can't find docker group with the default user.
What am I missing here?






linux docker




linux docker






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 2 days ago









Sam

6510




6510








  • 2




    only do a restart.
    – gopy
    2 days ago






  • 4




    Changes to group credentials don't affect your current session. You just need to log out and log back in; it's not necessary to restart.
    – larsks
    2 days ago






  • 1




    yup! Thanks, it worked. Log out and log in. P.S. why is it necessary?
    – Sam
    2 days ago
















  • 2




    only do a restart.
    – gopy
    2 days ago






  • 4




    Changes to group credentials don't affect your current session. You just need to log out and log back in; it's not necessary to restart.
    – larsks
    2 days ago






  • 1




    yup! Thanks, it worked. Log out and log in. P.S. why is it necessary?
    – Sam
    2 days ago










2




2




only do a restart.
– gopy
2 days ago




only do a restart.
– gopy
2 days ago




4




4




Changes to group credentials don't affect your current session. You just need to log out and log back in; it's not necessary to restart.
– larsks
2 days ago




Changes to group credentials don't affect your current session. You just need to log out and log back in; it's not necessary to restart.
– larsks
2 days ago




1




1




yup! Thanks, it worked. Log out and log in. P.S. why is it necessary?
– Sam
2 days ago






yup! Thanks, it worked. Log out and log in. P.S. why is it necessary?
– Sam
2 days ago














1 Answer
1






active

oldest

votes

















up vote
1
down vote













@larsks already replied to the main question in a comment, however I would like to elaborate on the implications of that change (adding your default user to the docker group).



Basically, the Docker daemon socket is owned by root:docker, so in order to use the Docker CLI commands, you need either to be in the docker group, or to prepend all docker commands by sudo.



As indicated in the documentation of Docker, it is risky to follow the first solution on your personal workstation, because this just amounts to providing the default user with root permissions without sudo-like password prompt protection. Indeed, users in the docker group are de facto root on the host. See for example this article and that one.



Instead, you may want to follow the second solution, which can be somewhat simplified by adding to your ~/.bashrc file an alias such as:



alias docker="sudo /usr/bin/docker"


Thus, docker run --rm -it debian will be automatically expanded to sudo /usr/bin/docker run --rm -it debian, thereby preserving sudo’s protection for your default user.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    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',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2fstackoverflow.com%2fquestions%2f53373592%2fdefault-user-not-added-to-docker-group-have-to-do-su-user%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








    up vote
    1
    down vote













    @larsks already replied to the main question in a comment, however I would like to elaborate on the implications of that change (adding your default user to the docker group).



    Basically, the Docker daemon socket is owned by root:docker, so in order to use the Docker CLI commands, you need either to be in the docker group, or to prepend all docker commands by sudo.



    As indicated in the documentation of Docker, it is risky to follow the first solution on your personal workstation, because this just amounts to providing the default user with root permissions without sudo-like password prompt protection. Indeed, users in the docker group are de facto root on the host. See for example this article and that one.



    Instead, you may want to follow the second solution, which can be somewhat simplified by adding to your ~/.bashrc file an alias such as:



    alias docker="sudo /usr/bin/docker"


    Thus, docker run --rm -it debian will be automatically expanded to sudo /usr/bin/docker run --rm -it debian, thereby preserving sudo’s protection for your default user.






    share|improve this answer



























      up vote
      1
      down vote













      @larsks already replied to the main question in a comment, however I would like to elaborate on the implications of that change (adding your default user to the docker group).



      Basically, the Docker daemon socket is owned by root:docker, so in order to use the Docker CLI commands, you need either to be in the docker group, or to prepend all docker commands by sudo.



      As indicated in the documentation of Docker, it is risky to follow the first solution on your personal workstation, because this just amounts to providing the default user with root permissions without sudo-like password prompt protection. Indeed, users in the docker group are de facto root on the host. See for example this article and that one.



      Instead, you may want to follow the second solution, which can be somewhat simplified by adding to your ~/.bashrc file an alias such as:



      alias docker="sudo /usr/bin/docker"


      Thus, docker run --rm -it debian will be automatically expanded to sudo /usr/bin/docker run --rm -it debian, thereby preserving sudo’s protection for your default user.






      share|improve this answer

























        up vote
        1
        down vote










        up vote
        1
        down vote









        @larsks already replied to the main question in a comment, however I would like to elaborate on the implications of that change (adding your default user to the docker group).



        Basically, the Docker daemon socket is owned by root:docker, so in order to use the Docker CLI commands, you need either to be in the docker group, or to prepend all docker commands by sudo.



        As indicated in the documentation of Docker, it is risky to follow the first solution on your personal workstation, because this just amounts to providing the default user with root permissions without sudo-like password prompt protection. Indeed, users in the docker group are de facto root on the host. See for example this article and that one.



        Instead, you may want to follow the second solution, which can be somewhat simplified by adding to your ~/.bashrc file an alias such as:



        alias docker="sudo /usr/bin/docker"


        Thus, docker run --rm -it debian will be automatically expanded to sudo /usr/bin/docker run --rm -it debian, thereby preserving sudo’s protection for your default user.






        share|improve this answer














        @larsks already replied to the main question in a comment, however I would like to elaborate on the implications of that change (adding your default user to the docker group).



        Basically, the Docker daemon socket is owned by root:docker, so in order to use the Docker CLI commands, you need either to be in the docker group, or to prepend all docker commands by sudo.



        As indicated in the documentation of Docker, it is risky to follow the first solution on your personal workstation, because this just amounts to providing the default user with root permissions without sudo-like password prompt protection. Indeed, users in the docker group are de facto root on the host. See for example this article and that one.



        Instead, you may want to follow the second solution, which can be somewhat simplified by adding to your ~/.bashrc file an alias such as:



        alias docker="sudo /usr/bin/docker"


        Thus, docker run --rm -it debian will be automatically expanded to sudo /usr/bin/docker run --rm -it debian, thereby preserving sudo’s protection for your default user.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 2 days ago

























        answered 2 days ago









        ErikMD

        1,8231318




        1,8231318






























             

            draft saved


            draft discarded



















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53373592%2fdefault-user-not-added-to-docker-group-have-to-do-su-user%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

            Can a sorcerer learn a 5th-level spell early by creating spell slots using the Font of Magic feature?

            Image
            28 6 $begingroup$ Per the Font of Magic feature, sorcerer can use Flexible Casting to create 5th-level spell slots at level 7, even though they are not typically available until level 9. You can transform unexpended sorcery points into one spell slot as a bonus action on your turn. The Creating Spell Slots table shows the cost of creating a spell slot of [5th level is 7] If such a sorcerer levels up while still having this 5th-level spell slot, can they choose a 5th-level spell as the spell they gain upon levelling up? The Spellcasting feature states: Additionally, when you gain a level in this class, you can choose one of the sorcerer spells you know and replace it with another spell from the sorcerer spell list, which also must be of a level for which you have spell slots.
            Read more

            Does disintegrating a polymorphed enemy still kill it after the 2018 errata?

            Image
            up vote 13 down vote favorite 1 After the 2018 errata, the disintegrate spell description now reads: A creature targeted by this spell must make a Dexterity saving throw. On a failed save, the target takes 10d6 + 40 force damage. The target is disintegrated if this damage leaves it with 0 hit points. If you were to polymorph an enemy into a rat and then disintegrate it, would the enemy be disintegrated or would it just return to its original form? I know that for Druids, it’s not an instant kill anymore, but is this the case for polymorph as well? dnd-5e spells polymorph errata share | improve this question edited 18 hours ago
            Read more

            A Topological Invariant for $pi_3(U(n))$

            Image
            3 3 $begingroup$ Recently, I saw a construction of topological invariant for $pi_3(U(n))$ with $ngeq 2$ : $$ N=frac{1}{24pi^2}int_{S^3} d^3x epsilon^{ijk} Tr[(U^{-1}partial_{x_i}U)(U^{-1}partial_{x_j}U)(U^{-1}partial_{x_k}U)] , $$ where $Uin U(n)$ depends on $boldsymbol{x}=(x_1,x_2,x_3)in S^3$ , $epsilon^{ijk}$ is the Levi-Civita symbol, $i,j,k=1,2,3$ , and the duplicated indexes are summed over. It is claimed that $N$ is an integer, but why? Update 02/02/2019 I think I got an argument for $n=2$ . In this case, $U=e^{i varphi} q$ with $qin SU(2)$ . Due to the trace and the Levi-Civita symbol in $N$ , $varphi$ does not contribute to $N$ . As $Tr[q^{dagger}partial_i q]=0$ and $(q^{dagger}partial_i q)^{dagger}=-q^{dagger}partial_i q$ , $q^{dagger}partial_i q$ in geneeral has the form $q^{dagger}partia
            Read more