1.0 beta - docker integration not working
I see that docker integration is not working under tools for me all i se in logs is
error connect EACCES /var/run/docker.sockSolution:Jump to solution
Found the problem. It's an issue with permissions within the container. I've created a pull request here
GitHub
fix: issue with docker socket permissions by Meierschlumpf · Pull R...
Homarr
Thank you for your contribution. Please ensure that your pull request meets the following pull request:
Builds without warnings or errors (pnpm buid, autofix with pnpm format:fix)
Pull r...
28 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
!qa required_data
Thank you for your question. Our support team has noted that your request does not meet the minimum required data so we are unable to answer your question.
Please provide:
- your Homarr logs
- your setup configuration (eg. docker compose, docker run, helm chart, screenshot, ...)
- A detailed description of your problem or question with additional images where necessary
- Your operating system
- Version of Homarr (do not say latest! say 0.15.2, ...)
Failure to comply with this will result in a permanent closure of your support request.
Only log is this one:
error connect EACCES /var/run/docker.sock
i use docker compose (TrueNAS dockge) and verison of homarr is 1.0.0-beta.5
For volume i have this as in docs:
volumes:
- /var/run/docker.sock:/var/run/docker.sockIt means that the container doesn't have permission to use the socket or docker is blocking usage (eg. by some docker socket proxy). Please ensure that the container has permission.
You might need to run as root to get it to run. Please note that PUID and GUID are not supported starting from 1.0 in favour of the user flag.
to add to this - I also can't use the docker integration - I have tried mapping
/var/run/docker.sock:/var/run/docker.sock as a path, and running with --user 0, and I've also tried using a docker socket proxy with the two new vars, DOCKER_HOSTNAMES AND DOCKER_PORTSI tested it and it doesn't work for me either. I tried setting up an admin user without success. Giving privileges doesn't help either.
Yep i also tried with user and checking path and not working
same here
running docker on syno
for me its not permission related for sure
using the same PUID and GUID or all 42 containers im running even portainer that just work
How do you know it's not? I'm curious.
Anyway, we use the same library to integrate so there should be no implementation difference.
As already mentioned, we do not support PUID and GUID.
ohw, didnt catch that note, mm wondering what i should o next then xD
is how my docker compose file looks like
discord make the text a bit mesy but the intentation are also perfect
Sorry, I don't not want to be offensive, but did you even read the documentation? The mounts are completely wrong for the 1.0 beta and we do not support the "dev" image yet and you should use the beta images.
We described the set-up instructions quite in detail on the blog post and the #📢・announcements . It would be nice if you follow them to avoid confusion & problems.
will read it again sry my bes im just really low on energy these days
No worries. I just want to remove any variables or side effects to isolate the problem. Let me know if it works afterwards
actually when i try homarr:latest im getting a manifest uknown error when trying to pull the image
Well... did you read the blog post / announcement post? We documented it there for you.
https://deploy-preview-113--homarr-docs.netlify.app/blog/2024/12/17/open-beta-1.0#how-to-use-the-beta-with-docker
Open Beta 1.0 | Homarr documentation
We are proud to announce the open beta of Homarr 1.0. This is a major milestone for us and we are excited to share it with you.
owh
didnt atch that post
will make the adjustment right now
In summary, we already adjusted the documentation for the final 1.0 release but the image hasn't been posted yet
ahw ok i will gently wait then haha i make de asjustment my config noew look like;
ow shit
beta xD
its pulling atm
thanks man and im trylu sry i was in a coma 2 years ago and the recovering goes really slow
whenever i improt the odl dashbpoard my username isnt working, i did the reset password command from console and it does generate a pwd but the interface doesnt recgonise the new passowrd as im kjeep getting invalid 😦
i must be doing something newby
if ur willing and having a bit of time to help me with this struggle
- Please slow down with message posting, no need to spam / complain
- This is a separate issue. Please ask in the existing thread about this in #💬・get-help .
got ya
removed all data and starting from scratch, the docker.sock still doesnt work do 😦
@Yossi did u got it working? if i may ask
No luck
ok thanks for notifying also on a synology by any chance?
I have the same problem, using docker on a Debian Container (on Proxmox), at the same time the old homarr instance can view and control docker without problems
Solution
Found the problem. It's an issue with permissions within the container. I've created a pull request here
GitHub
fix: issue with docker socket permissions by Meierschlumpf · Pull R...
Homarr
Thank you for your contribution. Please ensure that your pull request meets the following pull request:
Builds without warnings or errors (pnpm buid, autofix with pnpm format:fix)
Pull r...
following the thread this discord item can be closed, for some reason i cant close it