4. If you dont want hard memory limit enforcement:
lxc config set my-container limits.memory.enforce soft
5. Increasing file and inode limits
Since its entirely possible we may in the future wish to run multiple LXD containers, its a good idea to already increase the number of open files and inode limits, this will prevent the dreaded too many open files errors which commonly occur with container solutions.
For the inode limits, open the /etc/sysctl.conf and add the following lines, as recommended by the LXD project:
6. IP :
lxc network device add template-yakkety eth0 nic nictype=bridged parent=lxdbr0 name=eth0
cat | lxc config set template-yakkety raw.lxc - << EOF
lxc.network.0.ipv4 = 144.217.33.2/24
lxc.network.0.ipv4.gateway = 144.217.33.1
EOF
template-yakkety - . , !
, :
"The recommendation is that you configure the distribution in the container to have a static IP.
On Ubuntu/Debian, that's done through /etc/network/interfaces
LXC does support setting those for you from outside the container, but most distributions will then fail to boot or will just unset that preset data."
7. :
lxc config set _ security.privileged true
- .