Update cloud-container to latest to fix file exists error on network setup

[AbdelrahmanElawady]

Description

Update cloud-container to latest to fix file exists error on network setup. This new version of cloud-container should have Router Advertisement disabled before links are set up which should stop the kernel from getting a route that conflicts with the routes defined under seed config.

Logs indicate there is no error for disabling RA:

settign up environment
setting up system
seed directory: /seed
root directory: /new_root
found user root
found device with mac: 
found device with mac: 26:64:58:52:b2:ac
found device with mac: 36:95:fd:12:af:12
disabling router advertisements for 26:64:58:52:b2:ac
setting up (26:64:58:52:b2:ac)
disabling router advertisements for 36:95:fd:12:af:12
setting up (36:95:fd:12:af:12)
generating host ssh keys
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=114 time=48.770 ms

Routes for IPv6 also seems to be set fine according to network-config:

$ ip -6 r
301:8afa:1b85:5b6e::/64 dev eth1 proto kernel metric 256 pref medium
200::/7 via 301:8afa:1b85:5b6e::1 dev eth1 metric 1024 pref medium
fd37:6f37:6f73:2::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth1 proto kernel metric 256 pref medium
default via fd37:6f37:6f73:2::1 dev eth0 metric 1024 pref medium

network-config:

#cloud-config
ethernets:
  eth0:
    match:
      macaddress: 26:64:58:52:b2:ac
    dhcp4: false
    addresses:
    - 10.20.2.2/24
    - fd37:6f37:6f73:2::2/64
    gateway4: 10.20.2.1
    gateway6: fd37:6f37:6f73:2::1
    routes:
    - to: 10.20.0.0/16
      via: 10.20.2.1
    - to: 100.64.0.0/16
      via: 10.20.2.1
    nameservers:
      addresses:
      - 8.8.8.8
      - 1.1.1.1
      - 2001:4860:4860::8888
  eth1:
    match:
      macaddress: 36:95:fd:12:af:12
    dhcp4: false
    addresses:
    - 301:8afa:1b85:5b6e:3ea9:e137:2562:5ea/64
    routes:
    - to: 200::/7
      via: 301:8afa:1b85:5b6e::1

Changes

• RA will be disabled for containers deployed on ZOS nodes.

Related Issues

• Some deployed VMs can't reach the public network #2177
• what is the cause of file exists when routes are added cloud-container#22