Using Ansible to Manage Docker Containers

Search for a command to run...

Hmm.. do you have 3 groups to act like DEV, Test and PROD? The idea of using Ansible is awesome for containers. This is also neatly presented. 🙂
I didn't think about it that way but it's a good idea. It was mainly to prove I could group containers and deploy different applications to them using the same configuration files. I Might do that DevTestProd scheduling but then I'd need to setup a release pipeline for each env using something like Azure Devops. Check the repo in case you haven't: https://github.com/soyroberto/ansibledox
In Part 1 of this series we explored the friendly foundations of machine learning: Classification Regression Clustering Neural networks Training Testing Overfitting Decision trees Reinforceme

Machine Learning with Trufa and Paula: A Friendly Guide to How Models Learn

The Microsoft Copilot Ecosystem

I love words, I compile words and always search what they mean. My native language is español and to my surprise there are not that many on line. México where I'm from has no official online language

Hey everyone, Roberto here and there and everywhere! We've all worked with data, we've all felt the pain of waiting. When you build a beautiful Power BI report, but the data is from yesterday. You have to wait for the nightly refresh to see the lates...

Ansibledox is a practical learning environment for Ansible automation that uses Docker containers to simulate a multi-host infrastructure. It demonstrates how to deploy services and manage configurations across a group of hosts using Ansible playbooks.
The GIT repositosy can be found here: https://github.com/soyroberto/ansibledox/tree/main

•6 Docker containers running Ubuntu (ubuntu0-ubuntu5)
•SSH access via localhost on different ports (2222-2228)
•Root access with password authentication
•Isolated environments for safe experimentation
•Inventory management with logical host grouping
•Vault integration for secure credential storage
•Modular playbooks for different services and configurations
•Group-based targeting for selective deployments

•pair_1: ubuntu0, ubuntu1 (ports 2222-2223)
•pair_2: ubuntu2, ubuntu3 (ports 2224-2225)
•pair_3: ubuntu4, ubuntu6 (ports 2226, 2228)
•ubuntu_pairs: Parent group containing all pairs
•Ansible vault for password encryption
•SSH key-based authentication support
•Privilege escalation (become: yes) for administrative tasks
•cowsay: Fun command-line tool installation
•zsh: Shell environment configuration
•lolcat: Text colorization utility
•Test tools: SSH and connectivity validation
•Package installation and updates
•Configuration file management
•Service configuration and startup
•User environment customization
•Safe space to practice Ansible without affecting production systems
•Immediate feedback through container isolation
•Reproducible scenarios for training
•Test playbooks before production deployment
•Validate automation logic across multiple hosts
•Debug inventory and group configurations
•Automated testing of infrastructure code
•Validation of deployment procedures
•Integration testing for multi-host applications
•Easy to add more containers/hosts
•Flexible grouping for different scenarios
•Modular playbook design for reusability
•Clear separation of concerns
•Standardized playbook structure
•Version-controlled infrastructure code
•Encrypted credential storage
•Isolated test environments
•No impact on production systems