anchor.diff:  This usually happens when Selenoid is started in Docker container with custom command-line arguments, e.g.:
   
       $ docker run <some-args> aerokube/selenoid:some-version -limit 10
  -    
  +
   In that case you have to specify path to configuration file explicitly (`cm` tool does this automatically):
   
  -    $ docker run <some-args> aerokube/selenoid:some-version -limit 10 -conf /etc/selenoid/browsers.json 
  +    $ docker run <some-args> aerokube/selenoid:some-version -limit 10 -conf /etc/selenoid/browsers.json
   
   **Getting error: create container: Error response from daemon: client version 1.36 is too new**
   
  
positive.code: 
  . You are passing an `OVERRIDE_VIDEO_OUTPUT_DIR` environment variable pointing to a directory on the `host machine` where video files are actually stored
  . When passing custom arguments to Selenoid container (such as `-limit` or `-timeout`) you also have to pass `-video-output-dir /opt/selenoid/video` and mount host machine video dir to `/opt/selenoid/video`
      
  **Can't get VNC feature to work: Disconnected**
  
  Please check the following:
  
negative.code: == Frequently Asked Questions
  
  === Selenoid in Kubernetes
  
  We are very frequently asked whether it is possible to run Selenoid in https://kubernetes.io[Kubernetes] cluster. The answer is - **it is possible but we do not recommend doing this**:
  
  . Selenoid can **only** work directly with https://docs.docker.com/engine/api/latest/[Docker API] and was created to be run on a workstation or a virtual machine with Docker installed.
  . Kubernetes contrarily has a completely different https://kubernetes.io/docs/concepts/overview/kubernetes-api/[API] and **can be using Docker** as a container runtime backend. In some clusters https://github.com/rkt/rkt[rkt] is used instead of Docker and in that case Selenoid will not work.
  . Even if Selenoid works - **all browser containers will be started on the same Kubernetes node** where it is running.
  . So far as Selenoid is using Docker API directly - Kubernetes will not be aware of additional containers started by Selenoid. This is dangerous and **can potentially lead to overloaded Kubernetes nodes**.
  . You can only have **one Selenoid replica maximum**. This is because Selenoid internally stores a list of running sessions in memory.
  
  If you need Selenium in Kubernetes or https://www.openshift.com/[Openshift], we have a separate solution called https://aerokube.com/moon/[Moon].
  
  === Logs and Dirs
  
  