ansible-coreos-bootstrap
ansible-coreos-bootstrap copied to clipboard
[NOT MAINTAINED] bootstrap a coreos machine for control via ansible
As this project is [not maintained](https://github.com/defunctzombie/ansible-coreos-bootstrap/pull/48#issuecomment-411408972) [anymore](https://github.com/defunctzombie/ansible-coreos-bootstrap/commit/389fd919f8f5f6c4266b194a3b7ca67199f008ef), you're welcome to use [its fork](https://github.com/instrumentisto/ansible-coreos-bootstrap) by our team. We've switched to portable PyPy version of 6.0.0 which should resolve the recent issues...
In reference to defunctzombie's post here: https://coreos.com/blog/managing-coreos-with-ansible/ it seems like it would be better to do this in the /etc/ansible/hosts file instead of what is posted there: `ansible_python_interpreter="/home/core/bin/python"` (reason: https://github.com/ansible/ansible/issues/9650)...
When executing an Ansible playbook using the 'role' defunctzombie.coreos-bootstrap, the task which runs the bootstrap.ah script always fails with the message "/lib64/libssl.so.1.0.0: no version information available (required by /home/jmontes/pypy/bin/libpypy-c.so)" Ansible...
Some version changes are incompatible with old bootstrap attempts. I can think of a couple ways to handle this, but I just wanted to lodge it as a concern. Here's...
- update from 5.1.0 to 5.6.0 (current). File naming scheme changed, instead of pypy-VERSION it is pypy2-vVERSION. - change installation process to remove any existing pypy directory. Otherwise reinstalls fail....
While it would be great to use GPG or another validation mech, the easiest thing for now is to hard code the SHA512 of the pypy-2.4.0.tar.bz2 into the bootstrap.sh.... https://gist.github.com/pquerna/b8925406e445288368d2...
Hi everyone, I feel like the general design of the role is not following the normal "ansible way" if there is something like this. What do I mean by this?...
Hi, I go the following error when running ansible-playbook -i inventory/vagrant website.yml. The step to install docker-py and pull the container imagess seem successful. It failed at launching the container....
I was using this role without any problems so far, but suddenly it stopped working. Probably it's not compatible with newer CoreOS versions. When I try to execute the role...