Hacker News Reader

Usually when you ssh into the machine to fix something broken then forget to backport the changes to the ansible script.

The same thing could happen with docker, too.

You usually can't ssh into docker container because:

1) it usually doesn't have sshd

2) you change would be thrown away at nearest container restart or migration.

The only way for it to persist is to do the right thing, i.e. apply the change where you should and have the container rebuilt.

You don't need ssh to get into a docker container.

Definitely what luos said, but also you typically run repeatedly against the same machines, with changes on each run. This can lead to having a different environment depending on whether you ran once or multiple times. Conversely with Docker, you're essentially recreating from scratch every time you build the image, with some caching to make it fast though.

How about just when your current machine (e.g. Mac) has a different supported version of Python?

Disclosure: I work at Google on Kubernetes.

Umm, you install the version of tools and libraries you've standardized on, and check them in your unit tests?