docker-qBittorrentvpn VS Portainer

Looking at the Github issues for the container many seem to be in the same situation as you: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/issues There doesn't seem to be any activity from the developer either.

I'm trying to deploy the markusmcnugen/qbittorrentvpn image but I'm having issues.

- Docker container https://github.com/MarkusMcNugen/docker-qBittorrentvpn

In terms of downloading your "Linux ISO's" automatically, I highly recommend setting up a qbittorent/vpn combo docker container, such as this one. There's also an entire set of programs with docker containers youll see referred to as the "*arr" stack, which help to manage your collection, as well as automatically download your selected media as it becomes available. These are a bit trickier to set up, but once you have everything configured and running, they are a godsend.

why not use qbittorrentvpn. Auto kill switch, etc. https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/

Hey all, I'm pretty decent with normal networking on routers and switches, etc. but I know very VERY little about iptables. I am trying to fix an issue with a qBittorrent + VPN container. The VPN includes a script setting up a bunch of iptables rules to prevent leaks outside of the VPN. Script is located here: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/blob/focal/qbittorrent/iptables.sh

Been having issues with docker ever since I first tried it, I can't for the life of me access it on the supposedly open ports. Tried setting up this docker for usage in my home plex server with arr services.

I went with the qbittorrentvpn container.

So here's the situation. I have a seedbox at home. It is currently running this docker image: https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/ Which runs qBittorrent and OpenVPN. It's set up so that all of the torrenting traffic goes through the VPN while the rest of my seedbox can be used for other things without having to worry about the VPN. I access this seedbox using the WebUI, which works fine whenever I'm on the local network.

Have Sonarr, Radarr, Sabnzbd, qBittorrent/VPN (NordVPN just for qBittorrent, not on Usenet connections) running in containers on the NAS using Docker Compose. Had OMBI also connected, but has been troublesome as of late for me. Newshosting as my usenet provider, NZBGeek for usenet indexing, Rargb and Nyaa for torrents. Just joined a few private trackers, but those are manually managed and seeding day and night.

Portainer

> Any tips on the minimum hardware or VPS's needed to get a small swarm cluster setup?

From my testing, Docker Swarm is very lightweight, uses less memory than both Hashicorp Nomad and lightweight Kubernetes distros (like K3s). Most of the resource requirements will depend on what containers you actually want to run on the nodes.

You might build a cluster from a bunch of Raspberry Pis, some old OptiPlex boxes or laptops, or whatever you have laying around and it's mostly going to be okay. On a practical level, anything with 1-2 CPU cores and 4 GB of RAM will be okay for running any actually useful software, like a web server/reverse proxy, some databases (PostgreSQL/MySQL/MariaDB), as well as either something for a back end or some pre-packaged software, like Nextcloud.

So, even 5$/month VPSes are more than suitable, even from some of the more cheap hosts like Hetzner or Contabo (though the latter has a bad rep for limited/no support).

That said, you might also want to look at something like Portainer for a nice web based UI, for administering the cluster more easily, it really helps with discoverability and also gives you redeploy web hooks, to make CI easier: https://www.portainer.io/ (works for both Docker Swarm as well as Kubernetes, except the Kubernetes ingress control was a little bit clunky with Traefik instead of Nginx)

In this section, we will add Portainer to help us in managing our Docker containers. You can find more details about it here. To integrate Portainer into our EC2 project, we can follow these steps:

Git issues pointing to: https://docs.portainer.io/v/ce-2.9/start/install/agent/swarm/linux gives a ERR_TOO_MANY_REDIRECTS.

I am currently running Portainer, but webhooks (GitOps) appear to be broken ( [2.19.0] GitOps Updates not automatically polling from git · Issue #10309 · portainer/portainer · GitHub ) and so I cannot send webhook to redeploy a stack. So, looking for alternatives. Using this as a good excuse to learn more about docker and CI/CD etc.

A Synology NAS running Portainer (https://www.portainer.io/) running Paperless NGX (https://github.com/paperless-ngx/paperless-ngx)

This works better than I can possibly tell you.

I have an Epson WorkForce ES-580W that I bought when my mother passed away to bulk scan documents and it scans everything, double-sided if required, multi-page PDFs if required, at very high speed and uploads everything to OneDrive, at which point I drag and drop everything into Paperless.

I could, thinking about it, have the scanner email stuff to Paperless. Might investigate that today.

Paperless will OCR it and make it all searchable. This setup is amazing, I love living in the future.

> I've come to the conclusion (after trying kops, kubespray, kubeadm, kubeone, GKE, EKS) that if you're looking for < 100 node cluster, docker swarm should suffice. Easier to setup, maintain and upgrade.

Personally, I'd also consider throwing Portainer in there, which gives you both a nice way to interact with the cluster, as well as things like webhooks: https://www.portainer.io/

With something like Apache, Nginx, Caddy or something else acting as your "ingress" (taking care of TLS, reverse proxy, headers, rate limits, sometimes mTLS etc.) it's a surprisingly simple setup, at least for simple architectures.

casaos it just makes things like backups, offsite syncing and many other nas related things so much easier to manage. And gives you a proper nas like experience similar to that in which you'd fine on companies like tnas or synology. I actually also use it as a replacement for portainer when i don't need the more advanced features it offers

> I moved to docker swarm and love it. It's so much easier, straight forward, automatic ingress network and failover were all working out of the box. I'll stay with swarm for now.

I've had decent luck in the past with the K3s distribution, which is a bit cut down Kubernetes: https://k3s.io/

It also integrates nicely with Portainer (aside from occasional Traefik ingress weirdness sometimes), which I already use for Swarm and would suggest to anyone that wants a nice web based UI: https://www.portainer.io/

Others might also mention K0s, MicroK8s or others - there's lots of options there. But even so, I still run Docker Swarm for most of my private stuff as well and it's a breeze.

For my needs, it has just the right amount of abstractions: stacks with services that use networks and can have some storage in the form of volumes or bind mounts. Configuration in the form of environment variables and/or mounted files (or secrets), some deployment constraints and dependencies sometimes, some health checks and restart policies, as well as resource limits.

If I need a mail server, then I just have a container that binds to the ports (even low port numbers) that I need and configure it. If I need a web server, then I can just run Apache/Nginx/Caddy and use more or less 1:1 configuration files that I'd use when setting up either outside of containers, but with the added benefit of being able to refer to other apps by their service names (or aliases, if they have underscores in the names, which sometimes isn't liked).

At a certain scale, it's dead simple to use - no need for PVs and PVCs, no need for Ingress and Service abstractions, or lots and lots of templating that Helm charts would have (although those are nice in other ways).