Permission denied on /var/run/docker.sock

[Firesphere]

I'm not sure when this first started, but today after attempting to update Chadburn, I got this error:

Docker events error: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.48/events": dial unix /var/run/docker.sock: connect: permission denied

Which is quite new to me

[mrclschstr]

I have the same error. Just reverted back to the previous version.

[maietta]

Hi, @mrclschstr and @Firesphere,

Thank you for opening the issue ticket on this.

This project is undergoing a massive rewrite which is almost complete, but testing has not caught all the issues as of yet. I will try and get a fix in today, but note, you probably should revert back to the version that worked last for you.

All of the changes made yesterday were to bring the project current, then remove a core dependency in favor of the native Docker API, and work to address a few people's issues.

Also, I will try and update the new docs site as soon as it's live, to reflect which version we consider stable and a big warning about using any newer version in production until testing is complete.

I'll try and have a fix today!

[Firesphere]

Reverted for now, I'll re-pull the "latest" probably tomorrow (NZ time)

Funnily enough, with every push you've done over the last day, I got a notification from DIUN telling me there was a new release in Docker 😆 Now that I've pulled a specific hash, I expect I won't get it anymore...

[maietta]

Unfortunately, the path to get Chadburn to a modern state is extremely difficult and complicated.

I'm hoping to get a stable version out soon. The docs will get updated as soon as a new stable is out. Until then, I would absolutely stick with the old version you were using before. All of the recent commits are prep work.

[maietta]

EDIT: This reply was created by AI. While you are free to follow the guide and give it a try, the software is not yet ready for production. There are other issues needing to be addressed. AI's answer is below:

I've improved the documentation for Docker socket permissions in PR #120. The issue is related to the recent migration from fsouza/go-dockerclient to the official Docker client library. The PR explains the changes and provides updated guidance on how to handle permission issues. For users experiencing this issue, please try the solutions provided in the updated documentation.

[pifou25]

Hello, same issue for me, I didn't notice imediatly when it started to fail.
But I had to rollback to an older version from 2 years ago (v1.0.7 from May 2023) because there seems to be no intermediate version for rpi3b (arch arm/v7)

[maietta]

Hi, @pifou25. Thanks for letting me know.

I am yet unable to test this issue specifically but will be prioritizing this when I can get back to work on it. It maybe tomorrow before I can go back to work on it.

The recent flood of changes included a major rewrite of the core of the software, which unfortunately wasn't an easy task, and testing is not fully implemented.

I will work to try to complete testing, but also include distributions for more architectures such as the arm/v7 and 8 platforms. This particular issue you've addressed seems to be a tricky one to fix after the rewrite, as we're now talking directly with the Docker Events API instead of an intermediary and now depreciated helper library.

[Firesphere]

Quick check, is the new version now working? Or should I stick to the one I have?

[maietta]

Quick check, is the new version now working? Or should I stick to the one I have?

Stick with the one you have. Huge changes recently, and I haven't had the time to fix the last remaining problems in new versions.

I will try and get back to it maybe this week.

[danutzzzzz]

I'm not sure when this first started, but today after attempting to update Chadburn, I got this error:

Docker events error: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.48/events": dial unix /var/run/docker.sock: connect: permission denied

Which is quite new to me

Hi, i have the same issue, so ive pulled v1.0.7 and will await the fix to be released and this to be closed.

[markfqs]

Maybe because the docker image is using GID=969 for "docker" group, while my host sets GID=929 for "docker" group?

/ $ ls -l /var/run/docker.sock 
srw-rw----    1 root     992              0 Oct  3 04:00 /var/run/docker.sock
/ $ id
uid=1000(appuser) gid=969(docker) groups=969(docker)

chadburn 1.0.7 was running as root

I set the user on my compose yml file:

    image: premoweb/chadburn:1.9.5
    user: "1000:992"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    deploy:
      mode: global

Not sure if might break something else