Can you elaborate on that? I'm sure it's both true and false depending on your definition of "how and where it is run," but wondering what you had in mind specifically.
A container is basically a "virtualenv" for shell, and it's honestly better than that because:
- it's more general (it isolates every language, not just Python), and
- not even bigger (e.g. an Alpine Linux container is not that much bigger than the Python install in every virtualenv!)
Traditionally you do indeed have the problem that copying a shell script from one machine to another basically guarantees you nothing about how it will work. These days we deploy containers, which solve the problem, and that's why shell is used so much in the cloud (e.g. anything with Github Actions has a boatload of shell)
Even more on that: https://www.oilshell.org/blog/2021/07/cloud-review.html