Phill

> Did you have a reason to using that flag? Well, yes. So that the contents of `~/IOTstack/volumes` come back "as is". The general backup (everything non-database) includes the compose...

I wholeheartedly agree with your comments on `.env`. Serious "what on earth was I thinking at the time?" going on there. Although it isn't hidden, I also dislike `env.yml` in...

> Though I'm torn on if it'd be better to add to docker-compose.yml So, that would be a candidate for this "header" file too, right?

I really hate to be "All Mr Negative" twice in the space of 24 hours but I also can't endorse this proposed change. Let's work backwards. Q1: Why does Telegraf's...

That's true - for **most** images. The sequence: ``` $ cd ~/IOTstack $ docker-compose pull $ docker-compose up -d $ docker system prune ``` will update anything that doesn't get...

Perhaps look at this [alternative backup](https://github.com/Paraphraser/IOTstackBackup). It definitely won't downgrade anything and the backup doesn't stop the stack or take anything down. The biggest "hole" i'm aware of is that...

At the risk of telling you things you already know, there are three basic types of image/container to think about: 1. Images/containers that are in your `docker-compose.yml` and contain `image:`...

See if [this gist](https://gist.github.com/Paraphraser/4ea9b5ab17d9ba9febc22c27cadb0c54) helps at all.

Well, here's my service definition: ``` telegraf: container_name: telegraf build: ./.templates/telegraf/. hostname: iotstack restart: unless-stopped environment: - TZ=Australia/Sydney ports: - "8092:8092/udp" - "8094:8094/tcp" - "8125:8125/udp" volumes: - ./volumes/telegraf:/etc/telegraf - /var/run/docker.sock:/var/run/docker.sock:ro...

Just as an experiment, I removed the current user from the `docker` group, logged out/in to let it take effect, and tried to bring up telegraf: ``` $ docker-compose up...