We have approximately 100 containers per host and run into some problems during reboots because of a container that needs to start before the others.

The container in question is Tinc, a VPN service, and only then can some other containers start after that, as we expose the Private IP address generated by Tinc to our other VPN connected machines. If the containers start before Tinc, chaos ensues. Is there an easy way that we can make a container always restart in a specific order after a reboot? We use multiple docker-compose.yml files. Trying to avoid having to go and manually do it and start up a couple dozen stacks as there are bound to be things missed, or problems like miscommunication between my team on what should and shouldn't be up. Advice would be welcome!