Now docker becomes a good neighbor for the other providers - it looks like a provider, acts like a provider, talks like a provider :)
As I figured out recently - packer is smart enough to actually provide ssh proxy for ansible (through docker exec) automatically and we don't need to have a complicated local exec logic for ansible playbooks. Yeah, it still needs python - but with ansible for now we have no other way...
Also I removed the python3 image and replaced by vmx ubuntu stack build-macossdklibs110 - it's much more usable, especially because python3 pip needs build libs, so it's a good deal to have python3 role to be installed in the base build image.
Related Issue
fixes: #11
How Has This Been Tested?
Manually
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
Now docker becomes a good neighbor for the other providers - it looks like a provider, acts like a provider, talks like a provider :)
As I figured out recently - packer is smart enough to actually provide ssh proxy for ansible (through docker exec) automatically and we don't need to have a complicated local exec logic for ansible playbooks. Yeah, it still needs python - but with ansible for now we have no other way...
Also I removed the python3 image and replaced by vmx ubuntu stack build-macossdklibs110 - it's much more usable, especially because python3 pip needs build libs, so it's a good deal to have python3 role to be installed in the base build image.
Related Issue
fixes: #11
How Has This Been Tested?
Manually
Types of changes
Checklist: