Whenever you flush or change your firewall, it drops iptables for docker annoyingly, or if you are using a service that affect the iptables in general can make docker unusable.
When you restart docker, the restart command i added will make sure to restart the bot aswell. Without it, the bot will have to be manually started with
docker-compose up -d
Whenever you flush or change your firewall, it drops iptables for docker annoyingly, or if you are using a service that affect the iptables in general can make docker unusable. When you restart docker, the restart command i added will make sure to restart the bot aswell. Without it, the bot will have to be manually started with docker-compose up -d