Selfhosted

40767 readers

656 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

Uid/gid in docker containers don't match the uid/gid on the server? (feddit.it)

submitted 1 year ago by [email protected] to c/[email protected]

18 comments fedilink hide all child comments

Installed a new debian server, installed docker, but then now i have a problem with permissions on passed directories.

On the previous server, the uid/gids inside the docker container match the uid/gid on the real server.

Root is 0, www-data is 33, and so on.

On this new server, instead, files owned by root (0) in the container are translated to 1000 on the server, www-data (33) is 100032, and so on (+1000 appended to the uid)

Is this normal or did I misconfigure something? On the previous server I was running everything as root (the interactive user was root), and i would like to avoid that

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 1 year ago (1 children)

I fixed it:

for future reference:

from https://docs.docker.com/engine/security/rootless/#uninstall, run dockerd-rootless-setuptool.sh uninstall
delete the user data (warning: i wasn't using any docker volumes and i had no data to lose!!!) using the command that the previous script tells you
add your user to the docker group and use the traditional "run docker as root" way: https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user

[–] [email protected] 8 points 1 year ago (1 children)

Why go through all of that complexity when you could just sudo apt install docker?

[–] [email protected] 0 points 1 year ago (2 children)

i don't want to type sudo before each single docker command

[–] Voroxpete 14 points 1 year ago* (last edited 1 year ago) (1 children)

You can do that with regular docker. Just add your user to the docker group.

(don't forget to log out and log in again after adding new groups to your user)

[–] twiked 4 points 1 year ago (1 children)

Niche use case, but you can also use newgrp to run commands with a recently-added group to your user, without having to logout/login yet.

[–] [email protected] 1 points 11 months ago

Or start a new session by typing bash, when already in bash.

[–] [email protected] 5 points 1 year ago

So add your user to the new docker group made on install of that package and you'll be able to docker without sudo. You may need to relogin or newgrp docker before it works tho