Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Are you maintaining the snap image? #203

Open
antoine-gallix opened this issue Feb 28, 2024 · 6 comments
Open

Are you maintaining the snap image? #203

antoine-gallix opened this issue Feb 28, 2024 · 6 comments

Comments

@antoine-gallix
Copy link

There is a snap packaging of dry on the canonical snap store. Are you the maintainer of it? Do you support this? If so could you mention it in the install instructions. I hesitate to install a package that the author does not mention existing. The author of the snap says monch0

@antoine-gallix
Copy link
Author

antoine-gallix commented Feb 28, 2024

I tried anyway. It's on the edge repo. And it's not working. I hope it was no malware

@moncho
Copy link
Owner

moncho commented Feb 29, 2024

Hello! Yes, I did create the snap a long time ago and I have not updated it in a while.

It is not malware, just a forgotten installation method :)

@moncho
Copy link
Owner

moncho commented Feb 29, 2024

I have updated the snap and it should be working again. Can you give it another try, please, @antoine-gallix?

@antoine-gallix
Copy link
Author

antoine-gallix commented Mar 4, 2024

Ah, nice to hear!
I've installed successfully the following version through snap:
dry v0.11.2 139 latest/edge monch0 -

Now when I run the dry command I get the following error:

INFO[0000] Dry could not start: retrieve container list: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.44/containers/json?all=1&size=1": dial unix /var/run/docker.sock: connect: permission denied

I'm not sure what is the process that tries to access the docker socket, but it's not allowed. The socket has the following permissions:

Permissions Size User Date Modified Name
srw-rw----     0 root  4 Mär 14:35  /var/run/docker.sock

Running dry with sudo don't change the outcome.

@moncho
Copy link
Owner

moncho commented Mar 4, 2024

Hmmm and can you run the Docker client without problems? So, for example, docker ps works?

@antoine-gallix
Copy link
Author

antoine-gallix commented Mar 7, 2024

The docker socket belong to the docker group. My user also belong to this group. This setup is the one officially recommended to not have to run docker as root. I don't know how snap work regarding users, but it doesn't seem to be run by my user, other it would have access to the socket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants