Closed Bug 1234546 Opened 8 years ago Closed 8 years ago

look into switching Balrog to Docker


(Release Engineering Graveyard :: Applications: Balrog (backend), defect)

Not set


(Not tracked)



(Reporter: bhearsum, Assigned: bhearsum)



(1 file)

Balrog is currently using Vagrant to manage dev environments, which is a bit old and crufty. Switching to Docker would modernize us, and also be a big step towards the potential transition to being CloudOps hosted.
(In reply to Ben Hearsum (:bhearsum) from comment #1)
> I started looking into this a few days ago:

This is looking pretty darn good now. I've got a set of Docker images that are functionally equivalent to the Vagrant image, and reworked the config and wsgi files to support that. The patch also rips out the vendor library in favour of putting everything in I'm going to sit on it for a few days and look at it with fresh eyes before seeking review.
PR has all the details.
Attachment #8702620 - Flags: review?(rail)
Attachment #8702620 - Flags: review?(rail) → review+
Commit pushed to master at
Merge pull request #38 from bhearsum/docker

bug 1234546: Switch Balrog to Docker + uWSGI and a bit of cleanup. r=rail
Comment on attachment 8702620 [details] [review]
add support for Docker images

I merged this morning. All looks well, including my tests on aus4-dev. I've updated the docs at to reflect the changes.
Attachment #8702620 - Flags: checked-in+
Been actively using Docker for local dev for weeks now - this is done. Any subsequent work will be taken care of in new bugs.
Closed: 8 years ago
Resolution: --- → FIXED
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.