Docker group assignment doesn't affect the user
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm using Ubuntu 18.04. On the manual page on how to use docker without sudo it is written that user should add himself to the docker group and perform logout/login for changes to take affect. I created a group, added my user to that group, performed su $USER and then groups command started to show the group docker in the list of groups that my user is part of. But when I close the terminal and open it again I do not see that my user is part of docker group. I still need to perform su $USER command to be able to join to the docker group again.
Why this happens?
PS. However cat /etc/group always shows that my user is part of the docker group.
Update
I've also tried to logout/login from ubuntu - the result is same
Update final
Restarted the system once again and changes applied(now new terminal does see current user in docker group). Perhaps some problems with ubuntu 18.04 log out process
linux ubuntu permissions docker user-groups
asked Feb 1 at 11:46
maksmaks
1501112
add a comment |
I'm using Ubuntu 18.04. On the manual page on how to use docker without sudo it is written that user should add himself to the docker group and perform logout/login for changes to take affect. I created a group, added my user to that group, performed su $USER and then groups command started to show the group docker in the list of groups that my user is part of. But when I close the terminal and open it again I do not see that my user is part of docker group. I still need to perform su $USER command to be able to join to the docker group again.
Why this happens?
PS. However cat /etc/group always shows that my user is part of the docker group.
Update
I've also tried to logout/login from ubuntu - the result is same
Update final
Restarted the system once again and changes applied(now new terminal does see current user in docker group). Perhaps some problems with ubuntu 18.04 log out process
linux ubuntu permissions docker user-groups
asked Feb 1 at 11:46
maksmaks
1501112
add a comment |
I'm using Ubuntu 18.04. On the manual page on how to use docker without sudo it is written that user should add himself to the docker group and perform logout/login for changes to take affect. I created a group, added my user to that group, performed su $USER and then groups command started to show the group docker in the list of groups that my user is part of. But when I close the terminal and open it again I do not see that my user is part of docker group. I still need to perform su $USER command to be able to join to the docker group again.
Why this happens?
PS. However cat /etc/group always shows that my user is part of the docker group.
Update
I've also tried to logout/login from ubuntu - the result is same
Update final
Restarted the system once again and changes applied(now new terminal does see current user in docker group). Perhaps some problems with ubuntu 18.04 log out process
linux ubuntu permissions docker user-groups
asked Feb 1 at 11:46
maksmaks
1501112
I'm using Ubuntu 18.04. On the manual page on how to use docker without sudo it is written that user should add himself to the docker group and perform logout/login for changes to take affect. I created a group, added my user to that group, performed su $USER and then groups command started to show the group docker in the list of groups that my user is part of. But when I close the terminal and open it again I do not see that my user is part of docker group. I still need to perform su $USER command to be able to join to the docker group again.
Why this happens?
PS. However cat /etc/group always shows that my user is part of the docker group.
Update
I've also tried to logout/login from ubuntu - the result is same
Update final
Restarted the system once again and changes applied(now new terminal does see current user in docker group). Perhaps some problems with ubuntu 18.04 log out process
linux ubuntu permissions docker user-groups
linux ubuntu permissions docker user-groups
asked Feb 1 at 11:46
maksmaks
1501112
asked Feb 1 at 11:46
maksmaks
1501112
edited Feb 1 at 14:42
maks
asked Feb 1 at 11:46
maksmaks
1501112
asked Feb 1 at 11:46
maksmaks
1501112
asked Feb 1 at 11:46
maksmaks
1501112
1501112
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The overall X Windows system (Gnome, KDE, etc) is forking off the terminal with the credentials it already has without triggering a new login. You need to logout completely and then log back in again for the group membership change to take effect.
In the short term, instead of an su $USER command, you can run newgrp docker in any shell to get access to that new group.
answered Feb 1 at 12:55
BMitchBMitch
22717
is there any way not to do this on new terminal or after system restart or after logout/login?
– maks
Feb 1 at 13:12
@maks It doesn't sound like you've tried a logout/login from the question.
– BMitch
Feb 1 at 13:17
I've updated the question. Actually at first i wrote about logout/login process, but then encountered that it happens even in a new terminal window, so updated the question
– maks
Feb 1 at 13:27
@maks If you're seeing the issue after a full logout/login, then that's a bug/defect. Others have reported this which may apply to you: bugs.launchpad.net/lightdm/+bug/1781418
– BMitch
Feb 1 at 13:49
tried to addnewgrp dockerto bashrc file, but after that new terminal can't be opened. Is there some prrocess that could automatenewgrp docker?
– maks
Feb 1 at 14:21
|
show 1 more comment
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: 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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400962%2fdocker-group-assignment-doesnt-affect-the-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
The overall X Windows system (Gnome, KDE, etc) is forking off the terminal with the credentials it already has without triggering a new login. You need to logout completely and then log back in again for the group membership change to take effect.
In the short term, instead of an su $USER command, you can run newgrp docker in any shell to get access to that new group.
answered Feb 1 at 12:55
BMitchBMitch
22717
is there any way not to do this on new terminal or after system restart or after logout/login?
– maks
Feb 1 at 13:12
@maks It doesn't sound like you've tried a logout/login from the question.
– BMitch
Feb 1 at 13:17
I've updated the question. Actually at first i wrote about logout/login process, but then encountered that it happens even in a new terminal window, so updated the question
– maks
Feb 1 at 13:27
@maks If you're seeing the issue after a full logout/login, then that's a bug/defect. Others have reported this which may apply to you: bugs.launchpad.net/lightdm/+bug/1781418
– BMitch
Feb 1 at 13:49
tried to addnewgrp dockerto bashrc file, but after that new terminal can't be opened. Is there some prrocess that could automatenewgrp docker?
– maks
Feb 1 at 14:21
|
show 1 more comment
The overall X Windows system (Gnome, KDE, etc) is forking off the terminal with the credentials it already has without triggering a new login. You need to logout completely and then log back in again for the group membership change to take effect.
In the short term, instead of an su $USER command, you can run newgrp docker in any shell to get access to that new group.
answered Feb 1 at 12:55
BMitchBMitch
22717
is there any way not to do this on new terminal or after system restart or after logout/login?
– maks
Feb 1 at 13:12
@maks It doesn't sound like you've tried a logout/login from the question.
– BMitch
Feb 1 at 13:17
I've updated the question. Actually at first i wrote about logout/login process, but then encountered that it happens even in a new terminal window, so updated the question
– maks
Feb 1 at 13:27
@maks If you're seeing the issue after a full logout/login, then that's a bug/defect. Others have reported this which may apply to you: bugs.launchpad.net/lightdm/+bug/1781418
– BMitch
Feb 1 at 13:49
tried to addnewgrp dockerto bashrc file, but after that new terminal can't be opened. Is there some prrocess that could automatenewgrp docker?
– maks
Feb 1 at 14:21
|
show 1 more comment
The overall X Windows system (Gnome, KDE, etc) is forking off the terminal with the credentials it already has without triggering a new login. You need to logout completely and then log back in again for the group membership change to take effect.
In the short term, instead of an su $USER command, you can run newgrp docker in any shell to get access to that new group.
answered Feb 1 at 12:55
BMitchBMitch
22717
The overall X Windows system (Gnome, KDE, etc) is forking off the terminal with the credentials it already has without triggering a new login. You need to logout completely and then log back in again for the group membership change to take effect.
In the short term, instead of an su $USER command, you can run newgrp docker in any shell to get access to that new group.
answered Feb 1 at 12:55
BMitchBMitch
22717
answered Feb 1 at 12:55
BMitchBMitch
22717
answered Feb 1 at 12:55
BMitchBMitch
22717
answered Feb 1 at 12:55
BMitchBMitch
22717
22717
is there any way not to do this on new terminal or after system restart or after logout/login?
– maks
Feb 1 at 13:12
@maks It doesn't sound like you've tried a logout/login from the question.
– BMitch
Feb 1 at 13:17
I've updated the question. Actually at first i wrote about logout/login process, but then encountered that it happens even in a new terminal window, so updated the question
– maks
Feb 1 at 13:27
@maks If you're seeing the issue after a full logout/login, then that's a bug/defect. Others have reported this which may apply to you: bugs.launchpad.net/lightdm/+bug/1781418
– BMitch
Feb 1 at 13:49
tried to addnewgrp dockerto bashrc file, but after that new terminal can't be opened. Is there some prrocess that could automatenewgrp docker?
– maks
Feb 1 at 14:21
|
show 1 more comment
is there any way not to do this on new terminal or after system restart or after logout/login?
– maks
Feb 1 at 13:12
@maks It doesn't sound like you've tried a logout/login from the question.
– BMitch
Feb 1 at 13:17
I've updated the question. Actually at first i wrote about logout/login process, but then encountered that it happens even in a new terminal window, so updated the question
– maks
Feb 1 at 13:27
@maks If you're seeing the issue after a full logout/login, then that's a bug/defect. Others have reported this which may apply to you: bugs.launchpad.net/lightdm/+bug/1781418
– BMitch
Feb 1 at 13:49
tried to addnewgrp dockerto bashrc file, but after that new terminal can't be opened. Is there some prrocess that could automatenewgrp docker?
– maks
Feb 1 at 14:21
is there any way not to do this on new terminal or after system restart or after logout/login?
– maks
Feb 1 at 13:12
is there any way not to do this on new terminal or after system restart or after logout/login?
– maks
Feb 1 at 13:12
@maks It doesn't sound like you've tried a logout/login from the question.
– BMitch
Feb 1 at 13:17
@maks It doesn't sound like you've tried a logout/login from the question.
– BMitch
Feb 1 at 13:17
I've updated the question. Actually at first i wrote about logout/login process, but then encountered that it happens even in a new terminal window, so updated the question
– maks
Feb 1 at 13:27
I've updated the question. Actually at first i wrote about logout/login process, but then encountered that it happens even in a new terminal window, so updated the question
– maks
Feb 1 at 13:27
@maks If you're seeing the issue after a full logout/login, then that's a bug/defect. Others have reported this which may apply to you: bugs.launchpad.net/lightdm/+bug/1781418
– BMitch
Feb 1 at 13:49
@maks If you're seeing the issue after a full logout/login, then that's a bug/defect. Others have reported this which may apply to you: bugs.launchpad.net/lightdm/+bug/1781418
– BMitch
Feb 1 at 13:49
tried to add
newgrp docker to bashrc file, but after that new terminal can't be opened. Is there some prrocess that could automate newgrp docker?– maks
Feb 1 at 14:21
tried to add
newgrp docker to bashrc file, but after that new terminal can't be opened. Is there some prrocess that could automate newgrp docker?– maks
Feb 1 at 14:21
|
show 1 more comment
Thanks for contributing an answer to Super User!
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400962%2fdocker-group-assignment-doesnt-affect-the-user%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
