sanitation@lemmy.today to Technology@lemmy.worldEnglish · 2 days agoNetflix now requires every user profile to be tied to unique email addressarstechnica.comexternal-linkmessage-square111fedilinkarrow-up1221arrow-down14
arrow-up1217arrow-down1external-linkNetflix now requires every user profile to be tied to unique email addressarstechnica.comsanitation@lemmy.today to Technology@lemmy.worldEnglish · 2 days agomessage-square111fedilink
minus-squareflandish@lemmy.worldlinkfedilinkEnglisharrow-up1·1 day agodoes it run in docker and with a vpn like proton, which i not using? i dont wanna fire up nord again. been using transmission in an old container!
minus-squareAppoxo@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up1·13 hours agogluetun (a container) enables you to put every sort of container behind it to act as a kill switch. If you have a .conf or .ovpn file, you can plug it in there. But they also support many providers natively
minus-squaremlg@lemmy.worldlinkfedilinkEnglisharrow-up1·17 hours agoYes, example: https://hub.docker.com/r/dyonr/qbittorrentvpn tbh I would just combo a compose with a seperate qbittorrent and vpn container on the same pod. That way you can set proper iptable rules if needed and perma bind qbittorrent to the vpn interface.
does it run in docker and with a vpn like proton, which i not using? i dont wanna fire up nord again. been using transmission in an old container!
gluetun (a container) enables you to put every sort of container behind it to act as a kill switch.
If you have a .conf or .ovpn file, you can plug it in there.
But they also support many providers natively
Yes, example: https://hub.docker.com/r/dyonr/qbittorrentvpn
tbh I would just combo a compose with a seperate qbittorrent and vpn container on the same pod.
That way you can set proper iptable rules if needed and perma bind qbittorrent to the vpn interface.