I have observed this, but I think it may be an issue with LXD parsing config; possibly due to the size of fields containing cloud-init data.
When you cannot see any config as in this situation, try:
"lxc config edit <container>"
This will open an editor where you can manipulate the config YAML directly, and I believe you will see the same limit applied there - it appears to be an LXD default.
I have observed this, but I think it may be an issue with LXD parsing config; possibly due to the size of fields containing cloud-init data.
When you cannot see any config as in this situation, try:
"lxc config edit <container>"
This will open an editor where you can manipulate the config YAML directly, and I believe you will see the same limit applied there - it appears to be an LXD default.
This is worth mentioning to the LXD team.