#8399 Broken Docker Setup Guide and Config + werkzeug upgrade

unreleased
closed
None
General
2021-10-27
2021-10-25
No

I tried following the docker setup guide 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.

Related

Tickets: #8406

Discussion

  • Dillon Walls

    Dillon Walls - 2021-10-25
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -7,4 +7,4 @@
    
     I have created a branch which fixes these things and hopes to clarify a few points in the docs.
    
    -dw/
    +dw/8399
    
     
  • Dillon Walls

    Dillon Walls - 2021-10-25
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -3,7 +3,7 @@
     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 update to the `gunicorn` package to v20.x.x broke the `[server:main]` configs in our \*.ini files.
    +- 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.
    
     
  • Dillon Walls

    Dillon Walls - 2021-10-25

    Hmm, since this ticket changes the default location of where the allura data lives, this could break existing deployments that choose to upgrade.

    It would be nice to address this somehow, but I'm not sure how. These proposed changes are definitely a step above and required for a macos deployment, so we definitely want them, but we don't want to confuse/annoy loyal allura-ites.

     
  • Dillon Walls

    Dillon Walls - 2021-10-25
    • summary: Broken Docker Setup Guide and Config --> Broken Docker Setup Guide and Config + werkzeug upgrade
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -8,3 +8,5 @@
     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.
    
     
  • Dave Brondsema

    Dave Brondsema - 2021-10-27
    • status: open --> review
    • assigned_to: Dillon Walls
    • Reviewer: Dave Brondsema
     
  • Dave Brondsema

    Dave Brondsema - 2021-10-27

    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.

     
  • Dave Brondsema

    Dave Brondsema - 2021-10-27
    • status: review --> closed
     

Log in to post a comment.