- 1,196
- 395
- NAS
- DS418play, DS213j, DS3621+, DSM 7.0.4-11091
To enable Sonarr to communicate with my downloader client, I had to enter the IP of the downloader container in the Host field. Recognizing that restarting the downloader container may cause an IP change, I'm curious if there is a straightforward means to set a fixed IP to a container.
My Docker package presently yields container IPs as 172.17.x.y
Since I haven't found a compelling way to lock in a fixed IP, I thought I might assign an IP (via Portainer) with a high final octet value for "y" which I could then reference in Sonarr.
If I do this, some questions.
Is there another/better means to point Sonarr to my downloader container?
My Docker package presently yields container IPs as 172.17.x.y
Since I haven't found a compelling way to lock in a fixed IP, I thought I might assign an IP (via Portainer) with a high final octet value for "y" which I could then reference in Sonarr.
If I do this, some questions.
- Will the container IP I set through Portainer survive a container restart (or image update)?
- Is the 3rd quartet in the Docker IP always constant? If I restart Docker (ex. DSM update, machine maintenance, etc) will "y" be constant.
Is there another/better means to point Sonarr to my downloader container?