Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Have you tried deploying with
docker-compose and running
docker-compose up -d to start the containers? We are doing something similar and I have had great success with automating deployment and configuration with docker-compose and ansible.
Also, do you persist your volume layer on your db (i.e. -v /mydata/dir:/var/lib/mysql)? If so you can tear down the containers and reattach them each time to that same data store. lastly, have you dumped and restored the configuration table on deploy? This can be done with a custom script (dockerentry-point.sh that executes the container starts then deploys the table and inserts the config).
TAC runs better in docker with multiple containers than it does in one large 11gb container. by breaking TAC into a db, search, ect you get a faster deploy. we've broken out the command line and job server as well so that nothing is coupled. we've found that by doing this we've gotten tac down from 11gb to 1.356gb speeding our deployment with docker-compose and ansible.
Also, do you persist your volume layer on your db (i.e. -v /mydata/dir:/var/lib/mysql)? If so you can tear down the containers and reattach them each time to that same data store. lastly, have you dumped and restored the configuration table on deploy? This can be done with a custom script (dockerentry-point.sh that executes the container starts then deploys the table and inserts the config).
TAC runs better in docker with multiple containers than it does in one large 11gb container. by breaking TAC into a db, search, ect you get a faster deploy. we've broken out the command line and job server as well so that nothing is coupled. we've found that by doing this we've gotten tac down from 11gb to 1.356gb speeding our deployment with docker-compose and ansible.