On an older docker setup where I was using virtualbox and have my home directories shared (and allura is in my home dir) then running with `./allura-data` as a *local* path now causes this mongo error:
``` exception in initAndListen: IllegalOperation: Attempted to create a lock file on a read-only directory: /data/db, terminating ``` I think its because mongodb directories need certain permissions or abilities that don't work with the vbox shared mount. Workaround is to set `LOCAL_SHARED_DATA_ROOT` to an absolute path like it used to be. --- ** [tickets:#8399] Broken Docker Setup Guide and Config + werkzeug upgrade** **Status:** review **Milestone:** unreleased **Created:** Mon Oct 25, 2021 09:13 PM UTC by Dillon Walls **Last Updated:** Wed Oct 27, 2021 03:14 PM UTC **Owner:** Dillon Walls I tried following the [docker setup guide](https://forge-allura.apache.org/docs/getting_started/installation.html) on my macbook and almost immediately ran into trouble. There were a few things going on: - Docker changed how it works with virtualbox and docker-machine - macOS prevents even sudo from creating `/allura-data` - A recent upgrade of the `gunicorn` package to v20.x.x broke the `[server:main]` configs in our \*.ini files. I have created a branch which fixes these things and hopes to clarify a few points in the docs. dw/8399 p.s. the werkzeug package is due for an upgrade, so I'm doing that here and testing that it works on a local deployment. --- Sent from forge-allura.apache.org because dev@allura.apache.org 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.
