HeBee

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by HeBee

  1. Resolving my own issue. As the log said there already was a 'dev/net/tun' device, owned by root. I deleted that file manually and after the transmission_vpn container was able to start. I guess it was leftover from a failed start?
  2. Complete Unraid newbie here, moving over from Synology. I'm trying to get Transmission_VPN working on my new Unraid machine and hitting a very basic issue: the container simply fails to start. This is what I see repeatedly in the logs: Starting container with revision: 85d3b9633607f2d1fd58d21190a84a31a4cea7b8 Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists Starting container with revision: 85d3b9633607f2d1fd58d21190a84a31a4cea7b8 Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists Looking at the Unraid environment I notice that the Transmission_VPN docker is not creating a folder to store the configuration in /mnt/user/appdata/, which is the default set in Docker. I also have installed the Plex docker and that one is working fine. Any ideas? Do I need to manually set the container to create a config?