Closed tomponline closed 6 years ago
Example config file
[root@rh-vz01 lxc]# cat /var/lib/lxc/el7build01/config
# Template used to create this container: /usr/share/lxc/templates/lxc-download
# Parameters passed to the template:
# Template script checksum (SHA-1): 273c51343604eb85f7e294c8da0a5eb769d648f3
# For additional config options, please look at lxc.container.conf(5)
# Uncomment the following line to support nesting containers:
#lxc.include = /usr/share/lxc/config/nesting.conf
# (Be aware this has security implications)
# Distribution configuration
lxc.include = /usr/share/lxc/config/common.conf
lxc.arch = x86_64
# Container specific configuration
lxc.cgroup.memory.limit_in_bytes = 512M
lxc.cgroup.memory.memsw.limit_in_bytes = 1G
lxc.start.auto = 0
lxc.apparmor.allow_incomplete = 1
lxc.idmap = u 0 1258512 65536
lxc.idmap = g 0 1258512 65536
lxc.rootfs.path = lvm:/dev/VolGroup00/el7build01
lxc.uts.name = el7build01
# Network configuration
lxc.net.0.type = veth
lxc.net.0.flags = up
lxc.net.0.name = eth0
lxc.net.0.ipv4.address = 192.168.1.18/32
lxc.net.0.ipv4.gateway = 169.254.0.1
lxc.net.0.ipv6.address = 2a02::xxxx/128
lxc.net.0.ipv6.gateway = fe80::1
lxc.net.0.script.up = /usr/libexec/lxc/ctctl-netup
lxc.net.0.script.down = /usr/libexec/lxc/ctctl-netup
Start up debug log el7build01.log
BTW, did you know your issue template has the args for the debug log the wrong way around?
Says
lxc-start -n <c> -l <log> -o DEBUG
But should be:
lxc-start -n <c> -l DEBUG -o <log>
This seems to be a behaviour of CentOS 7, as its happening on the physical machine too:
cat /proc/mounts | grep ' / '
rootfs / rootfs rw 0 0
/dev/vda1 / ext4 rw,noatime,nobarrier,data=ordered 0 0
Seems quite strange, as it doesnt happen on debian 9 hardware nodes, or centos 6 hardware nodes.
The template below is mostly useful for bug reports and support questions. Feel free to remove anything which doesn't apply to you and add more information where it makes sense.
Required information
The output of
lxc-start --version
lxc-checkconfig
uname -a
cat /proc/self/cgroup
cat /proc/1/mounts
Issue description
When using LVM with LXC, the container shows duplicate
/
mount points inside the container.e.gThis confuses monitoring software as there are 2 root mounts.
For some reason, with a Debian host, this is not happening, and I'm not sure what the difference is.
Information to attach
dmesg
)lxc-start -n <c> -l <log> -o DEBUG
)