The stock image does all sorts of horrible things like modifying its own configuration at runtime and installing a variety of Python packages into attached volu

The stock image does all sorts of horrible things like modifying its own configuration at runtime and installing a variety of Python packages into attached volumes. So yes, you can "run" the stock image on k8s, if you abandon most of the advantages of deploying a container in the first place, but if you want to deploy it the way you would normally deploy a container, with the dependencies packaged into the image before it launches and tidily separated config & state, and have it behave predictably in future rather than just like a miniature pet server that needs care & attention, you have a little work to do.