2 ms·
No, you don't need those tools anymore. Cook a base VM image that has the docker engine and anything else you need. Do this once and spin up VMs you need after
by manigandham 9y ago
No, you don't need those tools anymore.
Cook a base VM image that has the docker engine and anything else you need. Do this once and spin up VMs you need after that. This is what images are for, and they're far easier, faster, more reliable and more secure than dealing with all this other junk.
- icebraining 9y agoHow do you do the cooking of the base VM image?
- sevagh 9y agoCheck out Packer (https://www.packer.io/intro/ https://www.packer.io/intro/)
- manigandham 9y agoAll the major clouds already have API commands to convert a VM into a reusable image - so a simple startup script + this API command is all you need. Even better since you can script all this too. If anything changes, update the startup script, then run this "make new base image" script and you're all set. Update VMs as needed. Really doesn't get much more complicated than that and using tools like ansible just to setup your VMs so you can run docker containers later is unnecessary.
- icebraining 9y agoYou make Ansible sound like an ICBM launching system. In practice, you do a simple "apt install ansible" once (on your machine) and then you write a simple startup script in it. There's nothing extra to be "unnecessary", it's a 1:1 replacement.
- manigandham 9y agoWhy do you need that then when you can just use the startup script directly with the VM? Unnecessary = not needed to function. Replacing functionality is just preference, which is fine, but specifically not necessary.
- icebraining 9y agoWhy do you need that then when you can just use the startup script directly with the VM? My point is that's a loaded question. You could just as easily ask why do you need bash in every VM when you can just have Ansible in a single machine.