demon.sh install error about kolide-quickstart

[juandanielpujols]

I made it work doing this:

1. "docker ps -a" showed an exited container kolidequickstart_fleet_1
2. "docker logs kolidequickstart_fleet_1" show "# A value must be supplied for --auth_jwt_key. This value is used to create...Consider using the following randomly generated key: tmvRVUPGasdffAYtWuGZ9Rzf"
3. copy key value
4. vi kolide.yml, in the auth section paste the key
5. docker rm -f $(docker ps -a)
6. ./demo.sh up

[groob]

Note: If you want to enroll the macOS host that this demo is running on you may have to edit the /etc/hosts file as specified in the output when generating the installer.

Did you do this yet? to connect to the fleet server, /etc/hosts should have a fleet entry.

[Maanpreet]

I'm facing same issue, Can't get it working,

Command
./demo.sh simple up

Starting kolidequickstart_redis_1 ...
Starting kolidequickstart_mysql_1 ...
Starting kolidequickstart_mailhog_1 ... done
Starting kolidequickstart_fleet_1 ... done
Waiting for MySQL to accept connections....
Waiting for Fleet server to accept connections.....................................................Error: Kolide failed to start up. Exiting.

This is what docker compose logs are complaining at the end

mysql_1 | 2018-01-14T00:47:06.782217Z 4 [Note] Aborted connection 4 to db: 'kolide' user: 'kolide' host: '172.18.0.5' (Got an error reading communication packets)
mysql_1 | 2018-01-14T00:47:06.795175Z 5 [Note] Aborted connection 5 to db: 'kolide' user: 'kolide' host: '172.18.0.5' (Got an error reading communication packets)

[ashvinashoke]

Manpreet, my issue was similar to yours if not the exact same. My Kolide App URL was set to the correct IP and port number, but the security group I had assigned to my EC2 instance wasn't configured properly. After adding my kolide app URL as an inbound rule and assigning an elastic IP to my instance, Kolide was able to start up properly.