Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug

What happened:
After upgrading from v1.9.2 -> v1.10.0-beta.2, containers using hostpath mounts are failing with:

        exitCode: 128
        finishedAt: 2018-03-12T19:25:03Z
        message: 'linux mounts: Path /opt/kubelet/dev is mounted on / but it is not
          a shared or slave mount.'
        reason: ContainerCannotRun
        startedAt: 2018-03-12T19:25:03Z

The message linux mounts: Path /opt/kubelet/dev is mounted on / but it is not a shared or slave mount seems like it's from the docker daemon, but the docker daemon was not updated during the upgrade so I had assumed a behaviour in the kubelet had changed that would cause this.

What you expected to happen:
Pod should be running as usual, but it fails with RunContainerError.

How to reproduce it (as minimally and precisely as possible):
Run Kubernetes cluster using host path mount.

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T21:07:38Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.0-beta.2", GitCommit:"63dad40a0391b7af32c34fdbf41fa199c3b247ad", GitTreeState:"clean", BuildDate:"2018-03-07T20:30:35Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release): Ubuntu
• Kernel (e.g. uname -a):
• Install tools:
• Others: