This template runs watchtower. This is new for me so still seeing if i like it! (fingers cross this works, yes need to setuyp smtp email at some point, lol)
none, this container can be cofigured entirely by env vars so i use those
none, no published port is needed
This is my most complex stack to date. It runs the unifi-poller (uPoller) application consisting of an influx database, grafana dashboard and the uPoller collector.
This has a lot of state (database, provisioning directory for granfa, state for grafana, config file for upoller, etc.)
This time i chose to store each of these in their own glusterfs volume mount using the gluster volumefs driver.
This has the advatages of creating folders that alread have the uid:gid of the grafan container (instead of messing around with chown and chmod)
This template runs my infinitude proxy instance. This enables Carrier Inifinity Thermostats to be controlled by API, web page, home assistant etc) One note please for the love of god never buy a carrier heating system with one of these controls they are terrible in my experience. I inherited it, instead buy a nice generic heating/AC system that can support any standard thermostat.
none, this container can be cofigured entirely by env vars so i use those
none, this published port of 4000 for this container oveeride the interall 3000 because i have container that needed 3000 it can be reached by swarmIP:4000
This template runs my cloudflare dynamic DNS updater. It adjust the default container cron job from 5 minutes to 1 minute because i have failover WAN ports.
none, this container can be cofigured entirely by env vars so i use those
none, this need no special port mappings or other considerations consider using an secret to store the API
This template deploys the portainer agent via portainer. I wanted a way to update the agent independently from the portainer web app. This is not a supported deployment architecture by portainer (which makes it odd they have the agent template in templates, any hoo)
none, this container can be cofigured entirely by the stack file
This template runs my experimental traefik server for evaluating if i move to it from handcrafted nginx proxy.
traefik requires a static configuration - you need to pick either file based on command line based (or all commands need to be in your stack). you cannot mix these - for example if you put some settigs in a file doing additonal static config via command line then things kike env vars will be ignored i chose to put the static config in a traefik.yml file this seems to be considerd best practice in 2.6 by some i also configured a dynamic files folder - this is for aything that can't or shouldn't be configured in a docker file (middlewares, non-docker related routers etc)
UPDATED 9/2/2023 - here we are a few years later, adguuard has been stable as heck now i wanted to add IPv6 to this mix these were the steps
| #!/usr/bin/env python3 | |
| """Command generator for setting DHCP Option 119 | |
| This script converts the specified domain names to DHCP Option 119 | |
| (Domain Search Option) and prints commands for various DHCP servers. | |
| USAGE: | |
| ./dhcp_option119.py DOMAIN ... | |
| EXAMPLE: |
I wanted a simpler way to assign gluster volumes in new stacks without having to create directories by hand There are variety of community plugins for this.
I chose to use this one https://github.com/chrisbecke/glusterfs-volume
It creates a directory called <stackname>_<volumename> for each volume defined in the stack.
Assume you setup glusterfs per this gist here
i wanted to update swarm images whenever there is a new image available (even at the risk of breaking something)
it seems watchtower can't do this for swarm stacks/services - only one off containers.
I found this great container from https://github.com/djmaze/shepherd
Must be placed on a manager node.