I see that at least some of the catalog apps expose the possibility of joining them to their own Docker network:
This would be pretty helpful for reverse proxy applications, where you only want the app accessible via the proxy–but as the tooltip says, the network must already exist. If you put in the name of a network that doesn’t exist, you see an all-too-familiar stack trace.
Sure, it isn’t hard to docker network create foo from the shell, but is there a way to do this through the GUI?
No, yes.
Not in TN GUI.
Yes in Portainer, Arcane., Dockhand. Dockge allows to join containers to container network, but not sure about creating the networks themselves (still have Dockge installed, but I’m all into Dockhand).
You could always have an init/startup script with the docket network commands.
I prefer to have everything in a docker compose file, or a docker manager, where I could move my containers quickly and without having to gather scripts etc.
There’s no need for that, as they persist–after I reboot the system, the Docker network is still present; it persists through system upgrades too. So it really is just a matter of running one shell command, once.
Sure, but the question is about the Apps system. I’m all-in on plain Compose at this point, and while this isn’t the only reason or even the biggest reason, it’s definitely on the list.[1] But I’m trying to keep Fester’s Guide up-to-date, and my assumption is that its intended audience will lean toward point-and-click.
The upshot is that it’s now possible to set up a reverse proxy, completely through the apps system, the way a lot of us use Traefik or Caddy: put all the apps on a proxy network, expose only the proxy to the rest of your network, and that way it can enforce TLS and any other controls you like. That’s a good thing, so I’ve updated my NPM guide (Nginx Proxy Manager | Dan's Wiki) to match. It’s just odd to me that that one step still needs to be done at the shell.
The biggest reason is that I just don’t trust iX to keep the apps ecosystem maintained, but I have to admit they’ve done better so far than I’d expected. ↩︎
I meant to have the docker commands in a script for when you have to move everything somewhere else (unless you keep good notes so you can redo the docker networking again).
I try to not need such ‘external’ setup and prefer to do it in the compose file.
Either by integrating everything needed (adguard + softether VPN) in the same compose file, or in rare cases, using the service/network names from another compose file.
My goal is to make my setups completely ‘portable’ (copy/paste) among the different servers I have/manage.
