Okay, I made myself a little bit more familiar with the documentation and now the profile for maas hosting containers looks like:
config:
boot.autostart: "true"
limits.cpu: "2"
limits.memory: 4GB
linux.kernel_modules: ip_tables,ip6_tables,netlink_diag,nf_nat,overlay
user.user-data: |
#cloud-config
packages:
- snapd
- ssh
- net-tools
- jq
- nano
- traceroute
- screen
- iptables
and the profile for containers hosting mysql, vault, haproxy looks like:
config:
boot.autostart: "true"
limits.cpu: "2"
limits.memory: 4GB
linux.kernel_modules: ip_tables,ip6_tables,netlink_diag,nf_nat,overlay
raw.lxc: lxc.mount.auto=proc:rw sys:rw
security.privileged: "true
I would like to thank you both for the PR link and brief explanation of the risk these options pose, but it unfortunately really does not resolve the problem
@tomp you mentioned some fixes to the DB and the fact that itβs not yet in snap.
When do you plan to implement it? It seems like the last hope
Thank you