Comment 24 for bug 1673411

Verified on xenial with a xenial lxd container and the provided instructions:

  Version table:
 *** 0.7.9-90-g61eb03fe-0ubuntu1~16.04.1 500
        500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages

$ lxc exec x1-fixed cat /run/cloud-init/result.json
{
 "v1": {
  "datasource": "DataSourceConfigDrive [net,ver=2][source=/config-drive]",
  "errors": []
 }
}

Inside the container:
root@foohost:~# find /config-drive/ -type f
/config-drive/openstack/latest/network_data.json
/config-drive/openstack/latest/vendor_data.json
/config-drive/openstack/latest/user_data
/config-drive/openstack/latest/meta_data.json
/config-drive/openstack/2015-10-15/meta_data.json
/config-drive/openstack/2015-10-15/network_data.json
/config-drive/openstack/2015-10-15/vendor_data.json
/config-drive/openstack/2015-10-15/user_data

And again, to make sure my config-drive was being read, I injected a failure:
$ lxc exec x1-fixed cat /run/cloud-init/result.json
{
 "v1": {
  "datasource": null,
  "errors": [
   "Unknown network_data link type: dvs-andreas-was-here-again",
   "Unknown network_data link type: dvs-andreas-was-here-again",
   "('ssh-authkey-fingerprints', KeyError('getpwnam(): name not found: ubuntu',))"
  ]
 }
}

All good.