I have also tried this both with the http://192.168... url and a custom https://home.server.com url. Same issue.
Docker image is running as root and regular disk: / works.
I don't want to hijack the issue, but I believe I'm dealing with the same issue. Mine is happening on an 11T software raid mounted at "/data". I'm wondering if the size is the problem, it being a Raid, or something else.
Of note, the order doesn't matter for me, it fails for "data" whether you put it first or second.
The disk mounted at "/" works just fine though, as does the memory and cpu. Since the disk mounted at "/" works, that leads me to believe it's not a problem with the docker volume, or permissions.
Again not trying to hijack anything, so we can focus on the reporter's issue (I'm not in a hurry). Just curious if his is a raid or not, and what the disk size should be showing.
version: "3.3"
services:
homepage:
image: ghcr.io/benphelps/homepage:latest
container_name: homepage
environment:
- PUID=1000
- PGID=970
- TZ=America/New_York
ports:
- 3000:3000
volumes:
- ./config:/app/config # Make sure your local config directory exists
- /var/run/docker.sock:/var/run/docker.sock:ro # (optional) For docker integrations
I'm hoping/thinking I just did something wrong with the Dockerfile because I cloned the repository and launched a dev environment and it worked just fine.
@slsnow I have an SSD as / and a HDD as /media/media. No raid, or NAS storage or anything like that. All local.
Ahh, that did the trick for me as well. I appreciate the help.
I'd like to explain my confusion for posterity sake, haha. I thought that the container was somehow running "df -kP" on the host itself. I wasn't understanding how "overlay" works in the container. I guess inside the container there is an "overlay" device, showing mounted at "/". It looks like "overlay" shares the same disk info inside the container as the host has (at least for the root device, or probably where the docker process is running). At least it has the same output when running "df -kP".
That explains why I was still getting proper output in homepage for the "/" disk, despite never having specified "/" as a volume when creating the container.
But the "data" device won't show and isn't mounted unless you specify it when creating the container. Now after having done that, within the container docker exec -it homepage, the "df -kP' output is as expected, and homepage is showing the info as expected.
Anyways, guess I need to do some more reading on the overlay2 driver, thanks guys. Enjoy your weekend.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.
Description
When trying to display a widget for my second disk resource it has an API Error with 404 Not Found.
My widgets.yaml
As you can see I have a second disk mounted at /media/media
This is what the browser shows:![image](https://user-images.githubusercontent.com/5943635/212984394-6a6cb58f-dfd0-48c7-8253-3f28a3cb8366.png)
I have also tried this both with the http://192.168... url and a custom https://home.server.com url. Same issue. Docker image is running as root and regular
disk: /
works.Steps to reproduce
homepage version
v0.5.10 (e1799f1, Jan 7, 2023)
Installation method
Docker
Configuration
Container Logs
No response
Browser Logs
`