What are /r/portainer's favorite Products & Services?

From 3.5 billion Reddit comments

For code block formatting on Reddit, prefix each line with four spaces:

that way you get a block of code that looks like this and doesn't do a single "block" for each line

Support for configuring the NordVPN container is a bit outside of what I can provide directly, but perhaps other users here have had experience with getting this set up and might be able to help out.

Interestingly, the README - I'm not sure which of the two is the correct value.

volumes: - /var/lib/docker/volumes/quassel-core/_data:/config

I don't think it's your issue, but I wouldn't recommend bind mounting like that. The /var/lib/docker/volumes directory is where named volumes are created, and assuming that you've already created one called quassel-core you can just refer to it like this:

volumes: - quassel-core:/config

as long as you also have a separate volumes definition (outside of the services section) defining it as external (ie, already created):

volumes: quassel-core: external: true

If the volume doesn't already exist and you want to create it, just leave out the external: true line.

As to your actual issue, I'd first start by taking the NordVPN container out of the equation and seeing if you can get quassel running on it's own. If so then the issue is with the NordVPN container and the routing therein, which at least gives you a place to start.

I know it's been a couple months since you posted, but did you get a chance to find a solution? I've been having a similar issue as you.

I don't personally use Gluetun (I use Bubuntux's NordVPN container for Wireguard) but tried the solution above, but it apparently doesn't work with Portainer. I was doing some research and it had something to do with how Portainer uses docker stack deploy. I think I even tried using version 2 in my compose file and was still unsuccessful. Maybe the solution for me is just to not use Portainer in this scenario?

Not on a separate docker host, no. Never even considered that as an option.

I did get them all running together on my Synology NAS, though. gluetun to create a Wireguard VPN tunnel to my Mullvad account, then the rest of the 'stack' (sonarr, radarr, jackett, qbittorrent, sabnzbd) all connect through the VPN container. It had the weird (to me) side effect of all of the open ports show up on the gluetun container, not on any of the others. So whatever it's local IP is, that's the IP that the sonarr port shows on, same with radarr, etc.

Essentially I wrote one big docker compose file, with the gluetun container at the top, and all the other containers having a 'network mode: "service:vpn" ' entry.

Generally in Kubernetes everything is created through manifests, which differs from Docker. In most situations you would be creating volumes in a deployment alongside your application. There's also a bunch of different types of volumes in Kubernetes, each with their own use cases and unique configuration requirements, which makes it difficult to build a one-size-fits-all web interface.

What you're likely looking for are Persistent Volumes, which in most cases are created using a Persistent Volume Claim by your deployment against an available Storage Class.

I do not think that is the issue for if I move Sonarr and Radarr outside of the NVPN container I can reach them but of course they can no longer communicate with NZBGet for that application is still routing through the NVPN container.