Adding routes from container host interfaces broken

[troglobit]

Both container host and bridge interfaces support setting routes inside the container. For bridge it seems to work fine, but for host interfaces (like VETH pairs) it is broken.

Example:

admin@infix-00-00-00:/> configure 
admin@infix-00-00-00:/config/> edit interface veth1a
admin@infix-00-00-00:/config/interface/veth1a/> set veth peer veth1b
admin@infix-00-00-00:/config/interface/veth1a/> set container-network route 0.0.0.0/0 gateway 192.168.1.1
admin@infix-00-00-00:/config/interface/veth1a/> show
type veth;
container-network {
  type host;
  route 0.0.0.0/0 {
    gateway 192.168.1.1;
  }
}
veth {
  peer veth1b;
}
admin@infix-00-00-00:/config/interface/veth1a/> end
admin@infix-00-00-00:/config/> set container system network interface veth1a
admin@infix-00-00-00:/config/> leave

Excerpt from show container log:

Mar 27 09:46:43 infix-00-00-00 container[4664]: Got networks: veth1a
Mar 27 09:46:43 infix-00-00-00 container[2555]: ^[[33mWARN^[[0m[0000] Error loading CNI config file /etc/cni/net.d/veth1a.conflist: error parsing configuration list: invalid character '{' looking for beginning of object key string 
Mar 27 09:46:43 infix-00-00-00 container[2555]: Error: unable to find network with name or ID veth1a: network not found

The generated CNI profile for veth1a looks like this:

root@infix-00-00-00:/etc/cni/net.d$ cat veth1a.conflist 
{
  "cniVersion": "1.0.0",
  "name": "veth1a",
  "plugins": [
    {
      "type": "host-device",
      "device": "veth1a",
          {
            "dst": "0.0.0.0/0",
            "gw": "192.168.1.1"
          }    }
  ]
}

Which gives us that both the IP address and "routes:" objects are missing/broken.

---

There is also no documentation/example for how to set routes for a container host interfaces.