[Feature] Add configuration option to flag a Docker install but specify a manual IP

[linglingpin]

I'm using Docker Desktop for Sonarr on a MacOS system. I tried to setup the cron job and had to specify the config file path due to path mismatch on Docker Sonarr. However, the script still cannot run due to path mismatch to the Sonarr libraries. Is it possible to add a setting to rectify this? Thanks.

sonarr-update-tba.bash :: 2025-07-21 11:50:39 :: [verb] Detected Sonarr v4, API v3
sonarr-update-tba.bash :: 2025-07-21 11:50:39 :: [info] Detected 2 libraries
sonarr-update-tba.bash :: 2025-07-21 11:50:39 :: [verb] - /data/TV Shows [Library ID: 4]
sonarr-update-tba.bash :: 2025-07-21 11:50:39 :: [verb] - /data/Anime [Library ID: 5]
sonarr-update-tba.bash :: 2025-07-21 11:50:39 :: [info] Checking for TBA/TBD items in /data/TV Shows
sonarr-update-tba.bash :: 2025-07-21 11:50:39 :: [error] Directory does not appear to exist: /data/TV Shows -- Skipping
sonarr-update-tba.bash :: 2025-07-21 11:50:39 :: [info] Checking for TBA/TBD items in /data/Anime
sonarr-update-tba.bash :: 2025-07-21 11:50:40 :: [error] Directory does not appear to exist: /data/Anime -- Skipping
sonarr-update-tba.bash :: 2025-07-21 11:50:40 :: [info] Located 0 files to process

[goose-ws]

What Sonarr image are you using? What does your 'containerIp' config option look like?

[linglingpin]

I'm using "ghcr.io/hotio/sonarr:latest" with network mode setup through gluetun VPN.

I'm using containerIp=("127.0.0.1").

When I used ("docker:sonarr"), the script stuck at "Checking API functionality" and later returned "[error] Curl returned non-zero exit code: 28". It seemed to get the Docker internal address "Container IP address: 172.18.0.2", is this where the problem is?

Thanks.

[goose-ws]

Yes, the issue is that if you don't have that docker:sonarr format for your container IP, then the script assumes it's a bare metal install, not a Docker install. And rather than check for your files in the docker container, it's going to check for them on bare metal.

I've never used the hotio Sonarr image, the issue is most likely that the config.xml probably doesn't exist at /config/config.xml like it does for the LinuxServer images.

Could you please give me the output of:

docker exec sonarr find / -type f -name config.xml

[linglingpin]

It does get the API key from config.xml correctly now, using docker:sonarr.

However it gets the IP address as 172.18.0.2 from the gluetun container. The script seems to unable to connect during "Checking API functionality".

[goose-ws]

Is your Sonarr networking being run through gluetun? If so, are you seeing the line:

Networking routed through another container. Retrieving IP address.

If it's retrieving the config correctly, it's likely something with your networking I haven't encountered before. During the IP retrieval? What is the final 'Built Sonarr URL:' value output?

[linglingpin]

Yes, it's going through gluetun.

The output is like this

sonarr-update-tba.bash   ::   2025-07-21 15:25:59   ::   [verb]  Networking routed through another container. Retrieving IP address.
sonarr-update-tba.bash   ::   2025-07-21 15:25:59   ::   [verb]  Container IP address: 172.18.0.2
sonarr-update-tba.bash   ::   2025-07-21 15:25:59   ::   [info]  Configuration file retrieved
sonarr-update-tba.bash   ::   2025-07-21 15:25:59   ::   [info]  Port retrieved from config file
sonarr-update-tba.bash   ::   2025-07-21 15:25:59   ::   [verb]  Port: 8989
sonarr-update-tba.bash   ::   2025-07-21 15:25:59   ::   [info]  API key retrieved from config file
sonarr-update-tba.bash   ::   2025-07-21 15:25:59   ::   [verb]  API key: xxxxxxxxxxxxxxxxxxxxxx
sonarr-update-tba.bash   ::   2025-07-21 15:25:59   ::   [info]  No URL base detected
sonarr-update-tba.bash   ::   2025-07-21 15:25:59   ::   [verb]  Built Sonarr URL: 172.18.0.2:8989/api/system/status
sonarr-update-tba.bash   ::   2025-07-21 15:25:59   ::   [info]  Checking API functionality

[goose-ws]

Ok, so if the function is working correctly, 172.18.0.2 should be the IP address for your gluetun container. Let's see what's happening when the script tries to call that. Could you give me the output of:

curl -svkL "172.18.0.2:8989/sonarr/api/v3/system/status" -H "X-api-key: YOUR_SONARR_API_KEY" -H 'Content-Type: application/json' -H 'Accept: application/json'

Replace YOUR_SONARR_API_KEY with your Sonarr API key. The line 7 of the output of curl will include the X-api-key header line, you can redact your API key or just remove that line entirely from the output. Nothing else it returns should be sensitive.

[linglingpin]

It just timed out trying to connect. But it connects right away if I change the IP address in the curl command to the computer's or 127.0.0.1.

*   Trying 172.18.0.2:8989...
* connect to 172.18.0.2 port 8989 from 10.15.20.58 port 51687 failed: Operation timed out
* Failed to connect to 172.18.0.2 port 8989 after 75001 ms: Couldn't connect to server
* Closing connection

[goose-ws]

Hm, so it's reachable over localhost, but not through gluetun? What does your compose blocks look like for Sonarr and gluetun?

[linglingpin]

I think it's because I'm using Docker Desktop and the host isn't able to connect to the Docker's network addresses.

[goose-ws]

Does Docker on Mac not route the Docker networks in a way that a user can reach them? Can you ping 172.18.0.1? Does ifconfig and/or netstat -r show a Docker gateway with that 172.18.0.1 address?

[linglingpin]

Yes, I'm not able to reach them this way. And the 172.18.0.1 doesn't show on either outputs.

Please see https://stackoverflow.com/questions/71336465/cant-access-docker-container-web-address-172-17-0-2-from-windows

I edited the bash script to point the containerIP to 127.0.0.1 and the script worked.

[goose-ws]

Oh, the problem is 'Docker Desktop', which is a non-configurable VM wrapper for 'Docker Engine'. That's why its network(s) aren't reachable from the user space -- it's a limitation of using the 'Docker Desktop' application, rather than the the user using 'Docker Engine'.

If you're happy with it manually edited, keep it that way, you'll just get false notifications about an update being available since your md5sum won't match mine. And you'll have to manually re-edit on future updates.

A configuration option that accommodates both Sonarr in Docker, and manually specifying the container IP, isn't currently in the scope. I could be add such an option in, at some point, but it won't be til I have time to get around to some of my more pressing to-do items first.