unable to start with example docker-compose: google analytics connection refused
Describe the Bug
upon starting of the example compose file:
puppetdb_1 | Running /docker-entrypoint.d/00-analytics.sh
puppetdb_1 | (/docker-entrypoint.d/00-analytics.sh) Sending metrics http://www.google-analytics.com/collect?v=1&t=event&tid=UA-132486246-1&an=puppetdb&av=6.9.1&cid=959c630d-4ab1-425b-a12b-8c39969b9b10&ec=production&ea=start&aip=1
puppetdb_1 | curl: (7) Failed to connect to www.google-analytics.com port 80: Connection refused
puppet_1 | Running /docker-entrypoint.d/10-analytics.sh
puppet_1 | (/docker-entrypoint.d/10-analytics.sh) Sending metrics http://www.google-analytics.com/collect?v=1&t=event&tid=UA-132486246-4&an=puppetserver&av=6.10.0&cid=738ddf10-14ec-41a8-a23f-97ccf103edc3&ec=production&ea=start&aip=1
puppet_1 | curl: (7) Failed to connect to www.google-analytics.com port 80: Connection refused
Expected Behavior
An example docker-compose stack that starts
Steps to Reproduce
from: https://puppet.com/try-puppet/open-source-puppet/download :
The fastest and easiest way to get started with Puppet is with PUPPERWARE, our Docker Compose-based stack. If you’ve got Docker and want to get started, just
- clone the repo https://github.com/puppetlabs/pupperware
- run docker-compose up
Environment
- Version puppet -> latest (as of 2020/04/24)
- Platform Manjaro(gnome) 20.0
- Docker: 19.03.8-ce, build afacb8b7f0
- Docker-compose: version 1.25.5
Additional Context
/
starting the same compose today and got passed it. IMO: Not being able to send analytics back to google when starting should not stop it from starting up.
Why does google need to be involved in any way?
Looks like you can turn off analytics with an ENV variable:
PUPPERWARE_ANALYTICS_ENABLED=false docker-compose up
Just stumbled upon this issue as well. Kind of disappointing that this sends metrics to Google without consent.