Robert Sachunsky

So to be clear about the proposal: - in [Testing the Docker installation](https://ocr-d.de/en/setup#testing-the-docker-installation) show a `docker run --user ... --volume ... -it ocrd/all bash` command, followed by the normal processor...

These recommendations are nearly complementary to the current dev-best-practice document. I believe this is rather urgent, since in the next weeks many new collegues will commence work. BTW, another example...

related: #112

@EEngl52 you mean the workflow guide, don't you? If you make a draft PR with how and where to put such info (i.e. parameters and recipes), then I (or others)...

Yes, good idea. I'll try to add the info somewhere in the wiki, and then close here. Hopefully it gets integrated into the workflow recommendations at some point (probably after...

> In the meantime this was already solved by adding the Docker calls in the respective sections of the user guide, wasn't it? https://ocr-d.de/en/user_guide#calling-several-processors No, that's not the same thing!...

So to sum up: - drop all the "via Docker" command examples in the user guide (as they are impractical and redundant) - explain once (at the top of the...

Am I the only one unsatisfied with documentation of the Docker option?

> You can mitigate that problem by using the `docker run --rm` option which will remove the container after executing the user guide already shows this each time, but not...

@jbarth-ubhd has this since been resolved?