title: What does "build artifact" mean in the context of a dockerized development environment?
body: <p>In a <a href="https://medium.com/on-docker/development-environments-with-docker-89657c7b4ea2#.6234qc9nf" rel="noreferrer">blog post</a> about creating a dockerized development environment there is a section where the following question and first paragraph answer are given:</p>
  
  <blockquote>
    <h3>What type of build artifacts do you want?</h3>
    
    <p>The build artifact I wanted in this example was a running container.
    Either Compose or docker would have been appropriate tools to that
    end. In your scenario you might prefer to have a distributable image,
    or you might prefer that the build produce a binary on your host
    operating system.</p>
  </blockquote>
  
  <p>I read in <a href="https://softwareengineering.stackexchange.com/q/106473/245542">another question</a> that an <em>artifact</em> can be anything created during a process. From reading through other answers it seems like the context in which the term is used is important.</p>
  
  <p>In the context of using <a href="https://github.com/docker/docker" rel="noreferrer">Docker</a> to create a development environment, what does <em>build artifact</em> mean?</p>