On 12/08/2015 02:21 PM, Peter Steele wrote:
In this case of course the containers are using the stock downloaded
CentOS 7 image instead of my custom image. I was unable to reproduce
the systemd error through multiple start/stop tests of my
containers. They always started up without any complaints. Granted,
these stock images are simpler than my custom images, but this seems
to point to something in my image that's causing this issue. At
least that gives me a bit to go on, although it's hard to understand
what additional rpm modules would cause systemd to behave this way
during bootup.
Are there specific lxc related configuration files needed in a CentOS
template that my custom image might not have? I'm asking because in
looking at /usr/share/lxc/templates/lxc-centos I see there are several
configuration steps that are performed against the installed CentOS
rootfs, such as disabling selinix, creating a minimal fstab, etc. Most
of these are already done as part of my image creation process, but I
see there are other steps I do not include, such as creating
/etc/init/lxc-sysinit.conf. This is done as part of a specific check for
CentOS release 6, so I wonder if there is something equivalent needed
for CentOS 7?
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users
