why-use-packer.md

aliases	category	classification	date	date_modified	draft	id	image	links	local_archive_links	pinned	print	series	tags	title	type
why-use-packer	packer	public	2021-02-28 03:15:14 -0800	2021-02-28 03:15:14 -0800	false	20210228111514				false	false		packer ansible ami image configuration devops	Why Packer?	tech-note

This is a good comment from Reddit on why you should use Packer.

Packer puts the config work into the image prior to deployment. This allows for ec2s or VMs to start much faster in time-critical situations. Sometimes installing packages on first boot can take a long time for networking and internet access to be ready. Then each vm has to do this configuration on each deploy. Putting config first you only pay the price to configure once, then you can deploy many times.

Doing config first also removes dependencies from deployment. The starting VMs don't need access to external repos (or the internet), etc. So it's easier to lock them down.

Baking images with packer also allows you to ensure all VMs are configured exactly the same (same package versions, CLI versions, etc) because they are created from the same image. Occasionally configuring after will run into issues with incomplete config runs so 2 VMs may be different even when they should be the same.

— TheRealKingGordon Why Packer?