I haven't been able to find any guides specific to running Fleet in Unraid. Seems like it would be pretty straight forward. I'm actually pretty new to using dockers and I've only been using Unraid for a couple of months. Here's my current docker setup. Fleet is failing here:

ts=2021-11-10T17:57:37.435547058Z mysql="could not connect to db: dial tcp 127.0.0.1:3306: connect: connection refused, sleeping 14s"

Failed to start: initializing datastore: dial tcp 127.0.0.1:3306: connect: connection refused

. I should learn to read.

exactly 🙂 I'm not sure how to define those settings

@Bryan have you configured the mysql parameters? https://fleetdm.com/docs/deploying/configuration#my-sql

making progress 🙂 where is this config stored?

The top of that linked doc provides that information 🙂

I sent env variables in docker settings, seems to take it when I dump config but the logs are still erroring out when I start the docker

Does that DB user need a password?

it's blank now, but when the docker starts it's trying to connect to 172.17.0.1 (fleet) instead of 172.17.0.2 (mysql)

In this screenshot (https://osquery.slack.com/archives/C01DXJL16D8/p1636574926105500?thread_ts=1636570775.103300&cid=C01DXJL16D8) it looks like it's configured for the correct IP. Do you still get an error about the other IP?

when I start the docker I get the errors highlighted in pink, when I log into the console of the docker and run "fleet config_dump" it shows the correct IP

172.17.0.3 is the IP of the server that is trying to initiate the connection, so I don't think it's trying to connect to the wrong host. You'd be getting a different error (like

could not connect to db: dial tcp: ...

) if it was trying to connect to a host where the MySQL server is not running.

Thank you @zwass I slept on it and revisited the mysql permissions, I had created the fleet user under localhost instead of 172.17.0.1 ... one step further now

Awesome. I was going ask what you were seeing 🙂

this is where I'm currently at. So looks like I need to set up my certs

Yep, or you can terminate TLS with a load balancer or proxy and have Fleet just serve HTTP. Either way works.

ok 🙂 getting closer but stuck again. Is there an administration page for Fleet that's supposed to load at :8080? or do I need the separate UI docker for that?

Yeah, you should now have the dashboard on port 8080

Woo! Thanks Everyone for the help! Looks like I may need to put together a guide for anyone else planning to use Unraid :D

That would be awesome! We'd happily promote anything you put together on our socials 🙂