Closed TusharVirk closed 1 year ago
Seems there needs to be a way to run docker-compose up -d
and regularly monitor the status of superset_node
. Whenever it exits (exit code 0 or otherwise), we need to run docker-compose down
and then docker-compose up
again. I think on initialization, it is running out of memory or something.
Tested latest PR today, and it updated properly.
Overview
Sometimes when pushing to production, the changes aren't reflected until after manually connecting to the container, running
docker-compose down
and thendocker-compose up
Expected behaviour
Any changes pushed to production should be reflected automatically without needing to manually restart containers.