2 ms·
I attempted to do something like this when figuring out our build problems but it didn't really work for me. It doesn't solve the problem of actually getting co
by __alexs 12y ago
I attempted to do something like this when figuring out our build problems but it didn't really work for me. It doesn't solve the problem of actually getting configuration into the build very well because it still relies on Dockerfiles and has the added side effect of making the cache mostly useless. Maybe I was just doing it wrong?
I also attempted to try Ansible for deploying containers and had issues with both of these bugs:
https://github.com/ansible/ansible-modules-core/issues/27 https://github.com/ansible/ansible-modules-core/issues/27
https://github.com/ansible/ansible-modules-core/issues/188 https://github.com/ansible/ansible-modules-core/issues/188
Do people actually use Ansible to control Docker in practice? It would be great to have something that was a step up from building random Python scripts from scratch :)
(Disclaimer: I'm not very good at Ansible.)
- aidanhs 12y agoFor my purposes, I wrote a makefile which starts up a container with ssh, then provisions it with ansible (as you would with any normal remote host). This meant a) I could reuse existing scripts to provision normal server b) docker could be used to test the ansible scripts were actually capturing everything required. The cache point was a bit of a pain though, I confess.
- zwischenzug 12y agoOur experience was that Dockerfiles were almost completely useless except for the most trivial of cases. We effectively ditched them, spitting out Dockerfiles that implant the ShutIt functionality and no more, eg: curl https://raw.githubusercontent.com/ianmiell/shutit/master/library/osquery/dockerfile/Dockerfile | docker build --no-cache -