Story #17344
Updated by Tom Clegg over 2 years ago
Resolve outstanding issues:
* Install arv-mount so a-d-c loopback driver can use it
* Avoid leaving system in inconvenient state if @arvados-server init@ doesn't go well
* Save a docker image (alpine linux?) during "init", and use it instead of arvados/jobs in diagnostics
* Document firewall / accessible port requirements
* Sanity-check dns/firewall early in @arvados-server init@
* Remove setup roadblocks (e.g., use PAM instead of Google API keys)