I'm running devstack from within a container I set up using ubuntu 16.04 (both the host and the container). I see this problem in the container:
stack@devstack-2:~/devstack$ ll /proc/sys/net/bridge/
ls: cannot access '/proc/sys/net/bridge/': No such file or directory
Whereas on the host it is ok:
stack@dl-360-116:~$ ll /proc/sys/net/bridge/
total 0
dr-xr-xr-x 1 root root 0 Aug 24 01:42 ./
dr-xr-xr-x 1 root root 0 Aug 23 20:47 ../
-rw-r--r-- 1 root root 0 Aug 24 01:42 bridge-nf-call-arptables
-rw-r--r-- 1 root root 0 Aug 24 01:42 bridge-nf-call-ip6tables
-rw-r--r-- 1 root root 0 Aug 24 01:42 bridge-nf-call-iptables
-rw-r--r-- 1 root root 0 Aug 24 01:42 bridge-nf-filter-pppoe-tagged
-rw-r--r-- 1 root root 0 Aug 24 01:42 bridge-nf-filter-vlan-tagged
-rw-r--r-- 1 root root 0 Aug 24 01:42 bridge-nf-pass-vlan-input-dev
Anybody knows how to configure lxd/lxc to add this path in the container?