Created
October 14, 2015 15:07
-
-
Save proffalken/a0c67a430f75b6548fb5 to your computer and use it in GitHub Desktop.
Docker Ansible TestKitchen CI Thoughts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ansible insists on using SystemD when running on Centos7, Docker and SystemD don't play well together, especially if you start to introduce DBUS into the mix as well (firewalld I'm looking at you!). | |
This is totally understandable as Docker is effectively a replacement for systemd (I know that's not strictly accurate, but for now it will suffice!) | |
The primary issue is that Ansible assumes that the process manager (upstart/sysV/SystemD) will be PID 1 and in Docker that's not going to be the case because it's a container meaning that we need to do shitty things like passing "use_docker" as an ansible extra var and then enable/disable in tasks appropriately, working around out testing infrastructure defeating the whole point of having it | |
I don't doubt that Docker is great for testing standalone applications or containers where you are only running Apache/MySQL/whatever but to test Ansible plays seems to be difficult because Ansible expects to see a system process manager and Docker doesn't have one :simple_smile: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment