anchor.diff:      $ docker version | grep API
   
   Then run Selenoid like the following:
  -    
  +
       $ DOCKER_API_VERSION=1.32 ./selenoid <rest-of-args> # As a binary
       $ docker run -e DOCKER_API_VERSION=1.32 <rest-of-args> aerokube/selenoid:some-version # As Docker container
   
  
positive.code: 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 
  
  **Getting error: create container: Error response from daemon: client version 1.36 is too new**
  
  
negative.code: 
  **Can I limit per-version browser consumption?**
  
  No, this is not supported. We consider the only reasonable limitation should be the overall browsers consumption. This is important to not overload the hardware.
  
  **How can I adjust Selenoid timeouts?**
  
  