Monopacker currently exists as a single repository that contains several builders used by the taskcluster team.

In order for other teams to use monopacker to generate their images, it should be easy to run monopacker with a completely separate set of builders, templates, scripts, and variables.

To that end, we should distribute monopacker as a docker image that allows a team to easily mount in their image generation configuration.

We have a docker image that works in CI for baking images. The process around that image isn't ideal - it isn't automatically created and uploaded to dockerhub. It's sufficient for CI purposes at present, though.