this post was submitted on 20 Oct 2023
3 points (61.5% liked)

Linux

8049 readers
88 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
[email protected]
3
"setfacl --modify" will get reverted after a reboot (lemmy.world)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
3 comments fedilink hide all child comments
 

A docker, when run for the 1st time, won't do so:

$ docker-compose -f docker-compose.local.yml up -d

permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.config-hash%22%3Atrue%2C%22com.docker.compose.project%3Doxygen%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied

I'll run this command

$ sudo setfacl --modify user:user1:rw /var/run/docker.sock

which will resolve the issue. However, after a reboot, the issue will arise again.

Why? How to make the change permanent?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

Because that file is created by the docker.socket service when the service starts and removed when it stops or reboots.

Changing the acl on system files is the wrong way.

Either put your user in the correct group or run docker in rootless mode.

Edit: docker should be the correct group.

https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user