Robert Sachunsky

> I'm not up-to-date: How are the containers run currently? Is it recommended that users do the `docker run` themselves or is there some kind of tooling we could change?...

Fixed by #362

> As this is designed as an OCR-D-Container-Systemtest, the workflow should focus on module integration, especially with known incompatibilities and, as to provide some sort of regression testing, on previously...

Should be fixed by #362 – please reopen if not.

> Same happens with `/.config` (where `ocrd resmgr` wants to create `ocrd`). > > I believe the reason for this is that when run as non-root, `HOME` is set to...

What's the status here?

> Besides spinning up multiple CLI-only containers (somehow) sharing volumes, we could also integrate containers as true network services, but merely by installing a thin OpenSSH server layer on top...

@joschrew I don't understand your logic here. You could easily bind-mount a NFS or other distributed storage, both on the Processing Server and on the Processing Worker and on the...

@krisstern have you tried to relax the numpy version requirement in the pyproject.toml build requirements? https://github.com/opencv/opencv-python/blob/6b73d90fc3e50ba6858926d299b49f0228e19d68/pyproject.toml#L11 See https://github.com/opencv/opencv-python/issues/713

> Another option would be to offer just making the new group an **alias** of the old one (as implemented via XSLT 1.0 in [workflow-configuration](https://github.com/bertsky/workflow-configuration/blob/master/mets-alias-filegrp.xsl)). @kba should we make that...