<p>You may use matchbox on a VM as you do on a baremetal machine, you won't be able to use packer on a baremetal machine ont he other hand as it doesn't handle any PXE boot option.</p>

<p>That said, leveraging vSphere/AWS/ API/cli to create a new machine from a template is usually quicker and more effective than using the API/cli to create the VM and then make it boot in PXE.</p>

<p>Packer will create machines, matchbox won't, it will allow you to match a profile with a machine but it won't rack your machine nor plug the networks and power cables, it won't do the machine creation neither for a VM, that not its goal.</p>

<p>So the main difference is the "before provisioning (chef)" step, as the machine creation, Packer will handle the machine creation whereas matchbox won't, matchbox will handle booting a blank machine and push the OS where packer usually won't. </p>

CC BY-SA 3.0
2018-01-22T19:45:01.343Z
This is exactly what I wanted thanks for the concise answer!
scott
CC BY-SA 3.0
2018-01-19T09:09:24.717Z
2018-01-19T09:09:24.717Z
Tensibai
<p>I have this setup to standup a baremetal machine:</p>



<pre class="lang-none prettyprint-override"><code>Terraform-&gt; Matchbox
         \-&gt; Chef-&gt; Docker
</code></pre>

<p>My colleague has a setup to standup VMs in AWS:</p>

<pre class="lang-none prettyprint-override"><code>Terraform-&gt; Packer-&gt; Chef-&gt; Docker
</code></pre>

<p>Is Packer to AWS as <a href="https://coreos.com/matchbox/docs/latest/" rel="nofollow noreferrer">Matchbox</a> is to Baremetal, in terms of image provisioning?  I know there not 1:1 in features since packer can provision chef and stuff (it seems, and so can terraform) but for the general purpose of standing up a machine can this be considered.</p>

<p>If not what is the difference between the two.  I am having trouble understanding exactly what packer is for (compared to matchbox), if it doesn't fit that relation.</p>

CC BY-SA 3.0
2018-01-18T23:50:57.840Z
Do you have a link to info on Matchbox?
Dave Swersky
<amazon-web-services><chef><terraform><packer><provisioning>
difference between packer and matchbox
scott
# difference between packer and matchbox

(Asked by: username_0 on 2018-01-18)

I have this setup to standup a baremetal machine:
Terraform-> Matchbox
         \-> Chef-> Docker

My colleague has a setup to standup VMs in AWS:
Terraform-> Packer-> Chef-> Docker

Is Packer to AWS as Matchbox is to Baremetal, in terms of image provisioning?  I know there not 1:1 in features since packer can provision chef and stuff (it seems, and so can terraform) but for the general purpose of standing up a machine can this be considered.
If not what is the difference between the two.  I am having trouble understanding exactly what packer is for (compared to matchbox), if it doesn't fit that relation.

**Tags:** amazon-web-services, chef, terraform, packer, provisioning

> **Comments:**
> **username_1**: Do you have a link to info on Matchbox?  

---

## 1 answers

### Answer by username_2 on 2018-01-19. Score: 5 | Accepted answer

You may use matchbox on a VM as you do on a baremetal machine, you won't be able to use packer on a baremetal machine ont he other hand as it doesn't handle any PXE boot option.

That said, leveraging vSphere/AWS/ API/cli to create a new machine from a template is usually quicker and more effective than using the API/cli to create the VM and then make it boot in PXE.

Packer will create machines, matchbox won't, it will allow you to match a profile with a machine but it won't rack your machine nor plug the networks and power cables, it won't do the machine creation neither for a VM, that not its goal.

So the main difference is the "before provisioning (chef)" step, as the machine creation, Packer will handle the machine creation whereas matchbox won't, matchbox will handle booting a blank machine and push the OS where packer usually won't.

> **Comments:**
> **username_0**: This is exactly what I wanted thanks for the concise answer!  

---

