LXC ls not showing proper names

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 :frowning:
@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 :slight_smile:
Thank you

1 Like

Are you still seeing errors in the log?

Yes, it is still there

Another theory is that the pool created by microceph somehow causes the issue. I created a very similar set of 7 machines using zfs pool and ls is working fine there.

I suspect the issue is caused by this:

Is there any chance it is going to be merged into edge snap anytime soon?

Yes its been merged so should be in the edge snap shortly, and will be in LXD 5.12.

It seems to have resolved the issue :slightly_smiling_face: thank you for your help :wink:

1 Like