May 15May 15 After updating to the latest stable release (7.3.0), my docker containers that have extra parameters set to use my vpn (--net=container:GluetunVPN) and network set to None, no longer startup. After some troubleshooting by removing the extra parameter, starting the docker container, re-adding the extra parameter and then starting back up the container, it is back up and working. Is there a better way to set the network container that should be used? Or do I need to remove the extra parameter and re-add it every time I stop the array from now on?
May 16May 16 I was able to get around this by just re-applying the current settings. Make a change to any setting, revert it and click “apply”.
May 25May 25 I have the same issue.The GPU in plex stops functioning because fail to send the extra parameters to Docker
May 25May 25 1 minute ago, milfer322 said:I have the same issue.The GPU in plex stops functioning because fail to send the extra parameters to DockerAnd your extra parameter is routing the plex docker through a VPN connection?
May 25May 25 1 hour ago, wgstarks said:And your extra parameter is routing the plex docker through a VPN connection?I stopped the general service docker and start, and it works nowthx Edited May 25May 25 by milfer322
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.