Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Thanks for using the TrueNAS Community Edition issue tracker! TrueNAS Enterprise users receive direct support for their reports from our support portal.

PLEX docker container not given proper nameserver / networking in SCALE

Description

I am using latest Nightly and trying to create a PLEX docker image.

During deployment it is not able to reach out to the internet to do the "claim" of the plex token. Going into the image itself it seems all requests are being directed instead to my network itself. For example trying to hit "https://plex.tv" with curl will go to my own hosted external service on port :443 instead.

Looking at the resolve.conf it doesn't include routing through any public DNS. Adding either my router or public DNS as a nameserver fixes the issue (but is obviously non-persistant).

The one it creates:

nameserver 172.17.0.10
search ix-plex.svc.cluster.local svc.cluster.local cluster.local <my network>
options ndots:5

What works:

nameserver 192.168.1.1
nameserver 1.1.1.1
search <my network>

I have the Kubernetes set to use my default adapter and point the gateway to my router. (settings.png)

In my network settings I have manual nameservers set, as well as the default route. (networking.png)

This is the summary of the plex creation:

Application Name: plex
Version: 1.1.0
Image repository: plexinc/pms-docker
Image Tag: 1.20.2.3402-0fec14d92
Image Pull Policy: Only pull image if not present on host
Configure Host Network: true
Port to expose for Plex UI: 32400
Enable Host Path for Plex Transcode Volume: true
Host Path for Plex Transcode Volume: /mnt/<location>
Enable Host Path for Plex Data Volume: true
Host Path for Plex Data Volume: /mnt/<location>
Enable Host Path for Plex Config Volume: true
Host Path for Plex Config Volume: /mnt/<location>
Plex Claim Token: claim-<claim token>
Plex container timezone: 'CST6CDT' timezone
Update Strategy: Kill existing pods before creating new ones
Confirm these settings.

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Adam Goldberg September 12, 2021 at 8:28 PM
Edited

 I came across this issue as well today and found a different cause and solution, sharing in case anyone else runs into this problem.

The domain I use in my network has a wildcard DNS entry, e.g. *.home.network.local resolves to the IP of my gateway (proxy). I also specified home.network.local as the domain of my network in TrueNAS scale network settings.

Since home.network.local gets added to /etc/resolv.conf in all the containers, any prepended host will resolve to an IP (my gateway) unless the final "." is specified. I was able to fix this by specifying an unresolvable domain in my truenas core settings (junk.network.local) and restarting the containers. This enabled dns resolution.

Waqar Ahmed May 10, 2021 at 8:36 AM

Waqar Ahmed May 7, 2021 at 9:07 PM

Awesome, please email me credentials at waqar@ixsystems.com then slightly smiling face Thanks!

Chris Griffith May 7, 2021 at 8:53 PM

Hi , sure that works!

Waqar Ahmed May 7, 2021 at 8:49 PM

would you be available for a session at 5 PM CST today slightly smiling face ?

Complete
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Impact

Low

Components

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created April 7, 2021 at 4:42 PM
Updated July 1, 2022 at 5:25 PM
Resolved May 17, 2021 at 6:21 AM
Configure