□ How ?Ĭopy the yaml file into some file where you have Ansible installed, lets say main.yamlĬhange: hosts, remote_user to match your target and run it. In the end Python 2 will not be even installed anymore so go ahead and create playbooks that will work in every possible situation, going back to shell scripts suddenly does not look as such a bad idea. Now we have modules that work under 2.7 up to some version, some now do not support Python 2 at all. on the other hand, we known that python 2 will be obsolete for years and Ansible kinda said meh. On one hand you can do so much quite easily and its maintainable. Honestly, this is my biggest love/hate with Ansilbe. Switching the playbook to python 3+ broke the package / yum module and suggested dnf module also did not work on Centos 7. this of course does not work with python 2.7. □īut thats mostly because I have tried to use git module to get the latest version number of docker-compose. So this was kind of shortcut ? I spend more time making sure this playbook works that it would take to do it manually. I had to update couple of Centos 7 servers that run old ( very very old ) docker. Than try to start your old containers and get: Error response from daemon: Unknown runtime specified docker-runc Why ? Usually this happens when you had old docker installed and upgraded to latest docker-ce version. I have also implemented fix that solve different runtime on containers if old docker was used. iPXE Boot Win/Linux iPXE Boot Win/Linux.Centos 7 docker Centos 7 docker Table of contents. ![]() ![]() Random Ansible Stuff Random Ansible Stuff.Random Docker Stuff Random Docker Stuff.K3s Cluster chassis K3s Cluster chassis.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |