stamina77

thanks ich777，i successful pass through nvidia card and installed plex under instruction of this thread https://www.geekbitzone.com/posts/2022/proxmox/plex-lxc/install-plex-in-proxmox-lxc/ It totally work as I expected，I can use nv card to encode video from unraid folder and port forward plex service on dedicated ethernet（not like orignal unraid docker failed to fulfill that purpose ) to pub connection now I have lots of interest to dive into lxc learning. Thanks ich777, you are the pro

yeah I changed : to = the error status disappear now in the container i can ls /dev/nvidia* -l and get the right result like crw-rw-rw- 1 root root 195, 254 Mar 12 16:32 /dev/nvidia-modeset crw-rw-rw- 1 root root 236, 0 Mar 12 16:32 /dev/nvidia-uvm crw-rw-rw- 1 root root 236, 1 Mar 12 16:32 /dev/nvidia-uvm-tools crw-rw-rw- 1 root root 195, 0 Mar 12 16:32 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Mar 12 16:32 /dev/nvidiactl the explore carries on

I have 2 nic on my mb, eth 0 for unraid main port (192.168.50.164) and use openwrt gateway (192.168.50.200) to connect to CA since I'm in China and its hard to connect to CA or dockerhub. eth 1 for docker dedicated use, I use it connect to main route ( ASUS AX11000 ) to host img like qbittorrent, transmission, plex and others that need direct linkage to pub since I can just port forward via eth 1. The plex docker issue is that If I use custom eth 1, I cant visit the local ip ( set plex ip to 192.168.50.5) via http://ip:32400/web, also port forwarding not succeed. However if I use eth 0 host for plex, the local net visit is fine but also port forwarding not ok. Weird things is the qb and tr docker is ok as the same setting as plex. So I turned into lxc to try yesterday, found its great and above network problem solved.

Hi ich777, I am trying to use LXC to solve my dual nic problem for plex container dedicated use and its work fine Problem is passting through nvidia card. I follow the instruction as this thread posted above and update my container config as my ls /dev/nvidia* -l result is as follow root@X13-Unraid:~# ls /dev/nvidia* -l crw-rw-rw- 1 root root 195, 254 Mar 13 00:32 /dev/nvidia-modeset crw-rw-rw- 1 root root 236, 0 Mar 13 00:32 /dev/nvidia-uvm crw-rw-rw- 1 root root 236, 1 Mar 13 00:32 /dev/nvidia-uvm-tools crw-rw-rw- 1 root root 195, 0 Mar 13 00:32 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Mar 13 00:32 /dev/nvidiactl /dev/nvidia-caps: total 0 cr-------- 1 root root 241, 1 Mar 13 00:32 nvidia-cap1 cr--r--r-- 1 root root 241, 2 Mar 13 00:32 nvidia-cap2 then I update the container config as follows # Template used to create this container: /usr/share/lxc/templates/lxc-download # Parameters passed to the template: --dist debian --release bullseye --arch amd64 # Template script checksum (SHA-1): 78b012f582aaa2d12f0c70cc47e910e9ad9be619 # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf lxc.arch = linux64 # Container specific configuration lxc.rootfs.path = dir:/mnt/os_cache/lxc/debian11/rootfs lxc.uts.name = debian11 # Allow cgroup access lxc.cgroup2.devices.allow = c 195:* rwm lxc.cgroup2.devices.allow = c 236:* rwm lxc.cgroup2.devices.allow = c 241:* rwm # Pass through device files lxc.mount.entry: /dev/nvidia0 dev/nvidia0 none bind,optional,create=file lxc.mount.entry: /dev/nvidiactl dev/nvidiactl none bind,optional,create=file lxc.mount.entry: /dev/nvidia-uvm dev/nvidia-uvm none bind,optional,create=file lxc.mount.entry: /dev/nvidia-modeset dev/nvidia-modeset none bind,optional,create=file lxc.mount.entry: /dev/nvidia-uvm-tools dev/nvidia-uvm-tools none bind,optional,create=file # Network configuration lxc.net.0.type = veth lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.name = eth0 lxc.net.0.hwaddr=52:54:00:04:EC:67 lxc.start.auto=0 After this, in the LXC tab the container shows faulty config error my unraid set is 6.12.8, the container img is debian 11

now it works perfect with the password, thanks

yes, whole process strictly follow the new method, I tried to create a new image and redo the su vncpasswd parameter things again. still the same log that the docker falled into a loop, I tried to use the docker terminal and get the error msg "Error response from daemon: Container 7bf0e24102efa03a307e8ef6850ee3cd41afd39050ebb7ec4c6168fa310e31d6 is restarting, wait until the container is running"

I tried to remove the variable and still couldnt connect , I strictly follow the process as the Firefox docker ( first su $user, than vncpassword, then add the variable)

Thanks man, I update the image and follow the method, after I edit the password and the parameters, the docker seems failed to start, I couldn't connect to the server (before the password config, the containter is ok) . Please check the log of the docker, it seems the docker fall into a loop but I cant figure out where the problem is.

surely i can wait, now I switch back to firefox docker to use vnc passwd certifacate, also thanks for the future update

does this also works for chrome docker? I tried this in chrome docker but not passwd required yet.