Stuck - /dev/net/tun issue
Hello,
Complete newbie to Linux, and trying to setup YAMS.
What I have done:
- Physically put together the setup. It is a Dell Optiplex micro with 2 external WD harddrives in a dedicated case connected by USB to the PC.
- Installed Debian 12. I kind of stumbled my way through the install, and later found some guides, but I don't think I messed too much up there. I found this AFTER the fact: https://www.linuxtechi.com/how-to-insta ... p-by-step/ the only differences I noticed was messing up my domain name or whatever and not selecting LVM on my harddrive.
- Connected my external HDDs and partitioned them as well as used mergerfs to pair them together into one location (/mnt/storage) following this guide: https://noted.lol/mergerfs-and-snapraid-setup-1/
- Followed the linked guide here: https://www.digitalocean.com/community/ ... in-as-root but most of it was pretty irrelevant, just made sure that my user had admin privileges (already did I think and setup the firewall.
- Tried to install YAMS from my user (not root)
First snag: was getting access errors for sed, which actually was solved by a restart.
New snag: I get to "Everything installed correctly! Starting YAMS services... This may take a while..."
11/12 succeed, except gluetun (I have been selecting "n" for the VPN as I plan only to use Usenet). I get an error:
Error response from daemon: error gathering device information while adding custom device "/dev/net/tun": no such file or directory
Failed to start YAMS services
And here I'm very lost. I can see that /dev/net exists, but not /tun. I can manually create a /dev/net/tun folder but then the install fails with a permissions error anyways, so I have since deleted the folder.
Any hints or ideas? I only found two resources, one on this forum (which was something to do with Proxmox) and this recent reddit thread: https://www.reddit.com/r/gluetun/commen ... g_did_you/ but I couldn't get those docker compose down and docker compose up commands to work because I don't have a config file, which I assume is due to the failed installation.