Replies: 5 comments 4 replies
-
|
I don't think the health check is the issue here. It seems like photon didn't start properly at all? What do the photon logs say? The health check will only show the container as healthy when the photon api is available. |
Beta Was this translation helpful? Give feedback.
-
|
I did some more digging and somehow, my PUID and PGID seems to have been ignored in favor of the default 9011 :-/ I stopped photon, did a |
Beta Was this translation helpful? Give feedback.
-
|
Here is my compose: |
Beta Was this translation helpful? Give feedback.
-
|
I just went through all the recent change-logs and found this, so I will go ahead and check again and report back here. |
Beta Was this translation helpful? Give feedback.
-
|
Update: Unable to check within the next few weeks as I am sourcing a new HD where photon's data was stored hence closing hte issue. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Looking at your Dockerfile it seems reasonable. This was all working so nicely when I was using
image: ghcr.io/rtuszik/photon-docker:devbut when you published version 1, I switched to latest. Any advice is welcome.I even copied it into my docker-compose.yml file to tweak it and slow it down:
but that didn't help as healthcheck error immediately start popping up as soon as I start the container.
It feels kind of random, as after a few restarts the container just works. And these healthchecks occur way more often than the above indicated 3 retries.
Beta Was this translation helpful? Give feedback.
All reactions