Replies: 4 comments 1 reply
-
|
Did you test the socket proxy directly? Like not through homepage |
Beta Was this translation helpful? Give feedback.
-
|
Yes, when SSH'd into the server I get get output from curl http://localhost:2375/containers/json [{"Id":"8304e5024ebd0a88ab88d3d65bcf0730a85091308f035875e9a36bd4db1612ce","Names":["/homepage"],"Image":"ghcr.io/gethomepage/homepage:latest","ImageID":"sha256:bbe936e53ecdc16497377c93270f37733a692af8f67828a113e02982172d03aa","Command":"docker-entrypoint.sh node server.js","Created":1760305461,"Ports":[{"IP":"0.0.0.0","PrivatePort":3000,"PublicPort":3000,"Type":"tcp"},{"IP":"::","PrivatePort":3000,"PublicPort":3000,"Type":"tcp"}],"Labels":{"com.docker.compose.config-hash":"d459257ce601cb59330b64befd0f5cd7f39911e4c079eaf45fce918a1f4ae1f7","com.docker.compose.container-number":"1","com.docker.compose.depends_on":"","com.docker.compose.image":"sha256:bbe936e53ecdc16497377c93270f37733a692af8f67828a113e02982172d03aa","com.docker.compose.oneoff":"False","com.docker.compose.project":"homepage-debug","com.docker.compose.project.config_files":"/home/docker/app-stacks/homepage-debug/compose.yaml","com.docker.compose.project.working_dir":"/home/docker/app-stacks/homepage-debug","com.docker.compose.service":"homepage","com.docker.compose.version":"2.34.0","org.opencontainers.image.created":"2025-09-22T15:23:40.735Z","org.opencontainers.image.description":"A highly customizable homepage (or startpage / application dashboard) with Docker and service API integrations.","org.opencontainers.image.documentation":"https://github.com/gethomepage/homepage/wiki","org.opencontainers.image.licenses":"GPL-3.0","org.opencontainers.image.revision":"4028194830f3b4a66706ba43ea6847e348a7dba0","org.opencontainers.image.source":"https://github.com/gethomepage/homepage","org.opencontainers.image.title":"homepage","org.opencontainers.image.url":"https://github.com/gethomepage/homepage","org.opencontainers.image.version":"v1.5.0"} ...I'm just now understanding the services.yaml portion. Seems you have to explicitly tell each service to use the docker proxy like this? - Actual Budget:
server: my-docker # <<< HERE
icon: sh-actual-budget.svg
href: https://budget.mynetwork.ca
container: actual-budgetThat now works but isn't stated in the doc and I'm only now understanding what that other user meant in the linked discussion Edit: Is there no way to set this globally? Edit 2: I guess it's eluded to here but not clear that the docker.yaml content is treated as a server and must be referenced even if using the proxy socket on the local host. |
Beta Was this translation helpful? Give feedback.
-
|
This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
|
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
Struggling to figure out what is incorrect in the setup and preventing the docker socket proxy from working. It works with the default root / direct socket setup. I've tried paring it down to just the bare minimum example from the doc and still can't get it to work.
homepage version
1.5.0 (bbe936e53ecd)
Installation method
Docker
Configuration
compose.yaml
docker.yaml
Container Logs
[2025-10-12T21:16:19.364Z] error: Error: connect ENOENT /var/run/docker.sock
at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1637:16)
at PipeConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)
Browser Logs
http://10.88.10.11:3000/api/docker/status/actual-budget
{
"error": {
"message": "connect ENOENT /var/run/docker.sock"
}
}
Troubleshooting
Tried all manner of variations with the compose and docker.yaml files to try and get it working, tried using the https example when running through my reverse proxy (caddy with https + certs), bypassed my reverse proxy by hitting homepage with the IP / port (http://10.88.10.11:3000). I even tried setting up something in the services.yaml like here even though I don't think that's required? Unclear though.
Even tried running it by an LLM with reference to the doc and can't figure it out what I'm missing.
Beta Was this translation helpful? Give feedback.
All reactions