Closed sajoupa closed 6 years ago
Starting with the release of LXC 2.1 we have renamed a bunch of configuration keys and marked their old versions as deprecated. LXC 3.0 has removed support for the legacy configuration keys that's why your config is failing. The list of new and old counterparts is:
Legacy Key | New Key | Comments
-------------------------------------|-------------------------------|---------
lxc.aa_profile | lxc.apparmor.profile |
lxc.aa_allow_incomplete | lxc.apparmor.allow_incomplete |
lxc.console | lxc.console.path |
lxc.devttydir | lxc.tty.dir |
lxc.haltsignal | lxc.signal.halt |
lxc.id_map | lxc.idmap |
lxc.init_cmd | lxc.init.cmd |
lxc.init_gid | lxc.init.gid |
lxc.init_uid | lxc.init.uid |
lxc.kmsg | - | removed
lxc.limit | lxc.prlimit |
lxc.logfile | lxc.log.file |
lxc.loglevel | lxc.log.level |
lxc.mount | lxc.mount.fstab |
lxc.network | lxc.net |
lxc.network. | lxc.net.[i]. |
lxc.network.flags | lxc.net.[i].flags |
lxc.network.hwaddr | lxc.net.[i].hwaddr |
lxc.network.ipv4 | lxc.net.[i].ipv4.address |
lxc.network.ipv4.gateway | lxc.net.[i].ipv4.gateway |
lxc.network.ipv6 | lxc.net.[i].ipv6.address |
lxc.network.ipv6.gateway | lxc.net.[i].ipv6.gateway |
lxc.network.link | lxc.net.[i].link |
lxc.network.macvlan.mode | lxc.net.[i].macvlan.mode |
lxc.network.mtu | lxc.net.[i].mtu |
lxc.network.name | lxc.net.[i].name |
lxc.network.script.down | lxc.net.[i].script.down |
lxc.network.script.up | lxc.net.[i].script.up |
lxc.network.type | lxc.net.[i].type |
lxc.network.veth.pair | lxc.net.[i].veth.pair |
lxc.network.vlan.id | lxc.net.[i].vlan.id |
lxc.pivotdir | - | removed
lxc.pts | lxc.pty.max |
lxc.rebootsignal | lxc.signal.reboot |
lxc.rootfs | lxc.rootfs.path |
lxc.se_context | lxc.selinux.context |
lxc.seccomp | lxc.seccomp.profile |
lxc.stopsignal | lxc.signal.stop |
lxc.syslog | lxc.log.syslog |
lxc.tty | lxc.tty.max |
lxc.utsname | lxc.uts.name |
Hi there, may I ask how to fix this "issue"? It seems I have the same problem. Of course, your post explained this issue clearly "config is failing" but I cannot figure it out how to fix this? My config is set by default. Since current LXC is 3.0, do I have to manually re-config manually? If so, how to do that? I'm sorry to ask such these naive questions. I'm a college student who just starts learning OpenStack. If you can point it out with any hints(like where I should go), it will be appreciated a lot! Thank you!
--update-- I searched old news for LXC 2.1, and found that I might use "lxc-update-config", but it said "lxc-update-config: command not found"
-----More background info ------ OS: Ubuntu 16.04LTS. How/Where I start: basically, follow the link here: https://www.ubuntu.com/download/cloud/try-openstack. Past progress: Install OpenStack without configuring anything a half month ago.
@zetelight You can change the config of a container with:
lxc config set $container_name raw.lxc "lxc.apparmor.profile=unconfined'"
or for a profile:
lxc profile set $profile_name raw.lxc lxc.apparmor.profile=unconfined
I don't have a conjure-up novalxd deployment to test right now, but ISTR that I updated the profile, not each container individually.
@sajoupa Thank you so much! It works for me now. Since I am not sure that I have set up any "profile", I update them for each container individually, Again, thanks for your help!
Required information
Issue description
I'm using nested containers. Physical machine: ubuntu 17.10, running lxd 3.0.0 (stable snap). Within a nested container (security.nesting=true), I run several lxds created with conjure-up. They've been running fine until today:
Here is the profile used by this containers:
I tested with the --edge lxd snap, and got the same result.
Steps to reproduce
According to http://manpages.ubuntu.com/manpages/xenial/en/man5/lxc.container.conf.5.html, the above setting should work ?
Information to attach
dmesg
)lxc info NAME --show-log
)lxc config show NAME --expanded
)lxc monitor
while reproducing the issue)