You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 9, 2020. It is now read-only.
I also want to use plex on the same box that runs LMS, and so cannot use host networking - which was the easiest networking mode to get working - because of port clash. The default bridge networking mode seemed to advertise the container IP address of 172.xxx.xxx.xxx which seemed to defeat autodiscovery.
Anyhow, I managed to get macvlan networking working, so thought others may appreciate an example.
The host has an ethernet interface eno1, and the subnet and gateway settings are the same as for that interface. The ipv4_address and ip_range settings are the ip address that the LMS server should be assigned. The ip_range needs to be a CIDR value. Strictly speaking I suppose ip range as a /32 isn't required, but i stopped fiddling when it started working!
Thanks for making this nice docker image.
Cheers
James
The text was updated successfully, but these errors were encountered:
Hi,
I also want to use plex on the same box that runs LMS, and so cannot use
host
networking - which was the easiest networking mode to get working - because of port clash. The default bridge networking mode seemed to advertise the container IP address of 172.xxx.xxx.xxx which seemed to defeat autodiscovery.Anyhow, I managed to get macvlan networking working, so thought others may appreciate an example.
The host has an ethernet interface
eno1
, and thesubnet
andgateway
settings are the same as for that interface. Theipv4_address
andip_range
settings are the ip address that the LMS server should be assigned. Theip_range
needs to be a CIDR value. Strictly speaking I supposeip range
as a /32 isn't required, but i stopped fiddling when it started working!Thanks for making this nice docker image.
Cheers
James
The text was updated successfully, but these errors were encountered: