Answers: <p>From <a href="https://www.spinnaker.io/reference/architecture/" rel="nofollow noreferrer">spinnaker own documentation</a></p>
  
  <blockquote>
    <p>Rosco is the bakery. It is used to produce machine images (e.g. GCE
    images, AWS AMIs, Azure VM images). It presently wraps <a href="https://www.packer.io/" rel="nofollow noreferrer">packer</a>, but
    will shortly be expanded to support additional mechanisms for
    producing images.</p>
  </blockquote>
  
  <p>So yes, rosco uses HashiCorp's packer.</p>
  
  <p>The main reason to use packer is that you just need to change the provider used to create a docker image or an AWS ami or an Azure image and keep your building step identical.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-09-08T12:11:48.987Z
Answers: 2017-09-08T12:32:10.020Z
Answers: 2017-09-08T12:32:10.020Z
Answers: Tensibai
Body: <p>I am confused. Does Spinnaker use HashiCorp's Packer for baking or is it another tool? The reason for asking this that a folder called packer resides in the github repo of rosco <a href="https://github.com/spinnaker/rosco/blob/master/rosco-web/config/packer/docker.json" rel="nofollow noreferrer">https://github.com/spinnaker/rosco/blob/master/rosco-web/config/packer/docker.json</a></p>
  
Tags: <cicd>
Title: Does Spinnaker's rosco use HashiCorp's packer or is it another tool?
UserDisplayName: 030
ThreadText: # Does Spinnaker's rosco use HashiCorp's packer or is it another tool?
  
  (Asked by: username_0 on 2017-09-08)
  
  I am confused. Does Spinnaker use HashiCorp's Packer for baking or is it another tool? The reason for asking this that a folder called packer resides in the github repo of rosco <https://github.com/spinnaker/rosco/blob/master/rosco-web/config/packer/docker.json>
  
  **Tags:** cicd
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-09-08. Score: 2 | Accepted answer
  
  From [spinnaker own documentation](https://www.spinnaker.io/reference/architecture/)
  
  > Rosco is the bakery. It is used to produce machine images (e.g. GCE
  > images, AWS AMIs, Azure VM images). It presently wraps [packer](https://www.packer.io/), but
  > will shortly be expanded to support additional mechanisms for
  > producing images.
  
  So yes, rosco uses HashiCorp's packer.
  
  The main reason to use packer is that you just need to change the provider used to create a docker image or an AWS ami or an Azure image and keep your building step identical.
  
  
  ---
  
  