IOTstack+OctoPrint: When your 3D printer turns on and off
The README.md at OctoPrint/octoprint-docker on GitHub contains the statement:
… we know that OctoPrint is not the best suited type of application for containerization, but we're working hard to make it as compatible as possible.
There is no elaboration on why OctoPrint is not "best suited" but it may have something to do with what happens when OctoPrint is running in a container and the 3D printer it is controlling is turned off: the container crashes and the service disappears.
Similarly, any attempt to bring up the OctoPrint service before the 3D printer has been switched on results in docker-compose refusing the jump because it can't satisfy the device mapping.