In theory you don't need to run 'build' stage if it is successfully completed at least once. And docker saves intermediate images and reuses them on rebuild if command in Dockerfile is not changed, so second rebuild should be faster. This is not true for some commands, e.g. solr image is always `wget`s solr.
I don't know what we can do regarding your first interruption, but the second one (pip install) implies that your image was already build, so you should be able to skip "build" stage in that case and just re-run `pip install`. Regarding "paster not found". Maybe deleting existing containers and then trying to run `pip install` again would help (`$ docker-compose rm`)? It should not require image rebuilding, you should have image in your cache already. That's right "allura_web" comes from the "web" image. Compose uses current directory + image name to give the name to the image, so if your allura code is not in the "allura" directory you should use `-p allura` for every `docker-compose` command. Unfortunately they don't provide a way to refer to current project name from config file, so "allura_web" just hardcoded there. One possibility is to upload prebuilt image to Docker Hub and use that in our `docker-compose.yml`, so that you fetch it once and reuse from cache whenever needed, but that's not really different from "build it once and reuse from cache whenever needed". Regarding mongo error. Do you have enough disk space available on your VirtualBox VM? Seems like mongo can't allocate files it needs. --- ** [tickets:#7806] Create a docker image for Allura** **Status:** in-progress **Milestone:** unreleased **Labels:** getting-started sf-current sf-4 **Created:** Fri Dec 05, 2014 07:02 PM UTC by Dave Brondsema **Last Updated:** Mon Jun 08, 2015 11:38 PM UTC **Owner:** Igor Bondarenko http://blog.dscpl.com.au/2014/12/hosting-python-wsgi-applications-using.html has a good starting point. Would be nice to support development config (supplanting our Vagrant image) as well as a production-ready config (for which we don't have any good docs/images currently) --- Sent from forge-allura.apache.org because [email protected] is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
