Re:Kubernetes Production Patterns and Anti-Patterns
by shykes on Saturday June 10, 2017 @07:42PM
(#14529848)
In this context it means preserving the default behavior of running the command specified in the image as PID 1, and not injecting any extra processes in the namespace. The difference in the runtime environment is subtle, but some applications rely on it. If we changed this default those applications would behave differently after upgrading to Docker 1.13 or later.
What does backwards compatibility mean in this context. The API?