Closed zehro closed 1 month ago
It might be because, similar to with Docker containers, the mapping of the "container" should be changed instead of the settings in Kapowarr.
P.S. the app should be updated to use version v1.0.0 instead of the older v1.0.0-beta-4
@Casvt I see. The chart listing is outdated (https://github.com/truenas/charts/blob/master/library/ix-dev/community/kapowarr/values.yaml)
I will attempt to install a custom docker image from https://hub.docker.com/r/mrcas/kapowarr, as it says it was updated 10 days ago. I will report back after seeing how it goes!
Edit: If you can also answer this question, what environment variable should I provide for a new base URL?
You don't set the base URL using an environment variable. You set it using the settings in the web-UI.
Right - there are two things that are a little difficult there.
Changing the port a containerised application is reachable via should be done via the 'app' in Truenas (similar to a port forward - think of the host as the router, and the container as the device).
The baseurl is done via the app itself, as it changes how it generates, listens to and replies to addresses for a proxy.
URL related - application. Port related - host.
Description of the bug
On the TrueNAS Scale app catalog, Kapowarr can be installed and runs out of the box. However, changing the port/base URL for reverse proxy reasons results in a failed startup probe. The app stays in "Deploying" status and the user has to manually edit the values in the Kapowarr.db to reset the settings.
To Reproduce
Expected behaviour
Kapowarr should start up normally.
Expected logs (running on default settings):
... and so on.
Screenshots
N/A
Version info
Running this as an app on TrueNAS SCALE (Dragonfish-24.04.1.1). Not really docker; more kubernetes until Electric Eel release.
Additional context
Related Kubernetes Events