Rancher 1.2 issues

1 and 2 are a result of using CNI for networking, the container is actually run with --net none. Technically the ports reported were never necessarily correct because we’ve always allowed you to change the host port on running containers and docker does not, so it would not be reflected in ps.

  1. Yes they are needed for the standard functionality. They are split up so that you can choose other implementations of e.g. networking. See http://docs.rancher.com/rancher/v1.2/en/faqs/troubleshooting/ “the subnet being used…”

  2. User-provided container names don’t make sense when they have to be unique with more than one instance on a host, during upgrades, etc. Generally once you’re using rancher people don’t actually use native docker very much. The rancher CLI has a ps that displays services.