figure out reliable way on how to get daemon.json onto production machines

uoft-tapp / tapp-cp

TA assignment and matching application (TAPP) & Contract Presentment helper (CP) at the Department of Computer Science, University of Toronto

8 stars 6 forks source link

figure out reliable way on how to get daemon.json onto production machines #13

Open gabriellesc opened 7 years ago

gabriellesc commented 7 years ago

Port of TAPP issue #157: https://github.com/uoft-tapp/tapp/issues/157

@jmzaleski:

currently, i wrote the comment in README file admonishing folks to create a daemon.json file on the host. How would one get it there from our repo?

jmzaleski commented 7 years ago

problem is that docker grabs the Docker0 interface when the services is started, long before our docker-compose files have any effect. So it has to go into /etc/docker of the machine hosting our containers. So we have an easy to forget, nasty, manual sys admin step before anotherwise vanilla VM is ready to run our system.

jmzaleski commented 7 years ago

hmm. we could put stuff in our run script to diff the /etc/docker/daemon.json file with the one in our repo and refuse to start (or complain) if different.. that would at least protect us from the omision.