Comment 6 for bug 1856832

As a test, I bootstrapped 2.7.1 AWS controller.
I added a machine, and deployed a test charm cs:~juju-qa/bionic/lxd-profile to a LXD container on that new machine.
It all looked ok:

$ sudo lxc profile list
+---------------------+---------+
| NAME | USED BY |
+---------------------+---------+
| default | 0 |
+---------------------+---------+
| juju-default-test-0 | 0 |
+---------------------+---------+

$ sudo lxc profile show juju-default-test-0
config:
  environment.http_proxy: ""
  linux.kernel_modules: openvswitch,nbd,ip_tables,ip6_tables
  security.nesting: "true"
  security.privileged: "true"
description: lxd profile for testing, black list items grouped commented out
devices:
  bdisk:
    source: /dev/loop0
    type: unix-block
  gpu:
    type: gpu
  sony:
    productid: 51da
    type: usb
    vendorid: 0fce
  tun:
    path: /dev/net/tun
    type: unix-char
name: juju-default-test-0
used_by:
- /1.0/containers/juju-b95fdf-0-lxd-0