Update:

I fixed it using freedog96150's solution, seen here:
https://community.easyengine.io/t/services-and-sites-not-restarting-on-reboot/14195/2

Solution Summarized:

1. Disable each site on droplet individually with: sudo ee site disable sitename.com
2. Run docker-compose down && docker-compose up -d (must cd into the services directory beforehand)
3. Re-enable each site on droplet individually with: sudo ee site enable sitename.com

His theorization on why this happens is interesting. I guess no fix has been employed by EasyEngine to allow a more organized start up process.

from easyengine.

Additional info:

If I run:
ip -br a

One of the things I see in the output is:
docker0 DOWN 10.0.0.1/24

This Networking Configuration Issues article at Digital Ocean makes it sound like it shouldn't be that way:
https://docs.digitalocean.com/support/check-your-droplets-network-configuration/

I can not run ifup, however, because I would need to install ifupdown with:apt install ifupdown, and as I have already established above, my droplet isn't able to connect externally.

from easyengine.