Awesome. I understand single-user instances aren't the primary focus - but upgraded docs for docker will be great. I think I've figured it out by reading the docker code & fiddling a bit, but my currently soapbox install is just unzipped in the container which isn't perfect from a upgrading/robustness point of view

I assume the best practise would be
* run 1 instance of rebased stricly as an api backed with a DB
* run 1-x instances of soapbox pointed to the API container depending on traffic/High Availability desires. (with the usual load balancer/ingress in front of them)
This would allow me to review/merge upgrade PR's as new docker tags become available independently for both streams and avoids (most) downtime when updating