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.