<div dir="ltr">Hi Scott,<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 15, 2013 at 1:17 PM, Scott Dowdle <span dir="ltr"><<a href="mailto:dowdle@montanalinux.org" target="_blank">dowdle@montanalinux.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Greetings,<br>
<br>
I'm working with a community member that is in the process of building a new Arch OS Template to contribute. Arch switched to systemd as their default init system some time ago. Fedora was the first distro to adopt systemd and it took a little while before Fedora OS Templates with systemd were working properly. I believe some changes to vzctl and the dists/scripts stuff had to be done so that systemd would work properly inside of an OpenVZ container.<br>
<br></blockquote><div><br></div><div>I'm glad someone is working on getting Arch working under OpenVZ.</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
So, the new Arch OS Template works fairly well but there are some error messages at startup... but they don't seem to hurt anything really as the container starts... but it would be nice to get rid of the errors.<br>
</blockquote><div> </div><div><br></div><div><br></div><div>Works out of the box for me with OSTEMPLATE="arch" in my VZ configuration.</div><div><br></div><div style>I do get the following errors on vzctl start :</div>
<div style><br></div><div style><div>cp: cannot stat '/etc/conf.d/netcfg': No such file or directory</div><div>grep: /etc/conf.d/netcfg.bak: No such file or directory</div><div>A unit file for profile 'venet0' already exists</div>
<div><br></div><div style>But container starts and everything appears to work properly (including network).</div><div style><br></div><div style>However, I notice the SSH keys are bundled with the template, which means every containers deployed with that template get the same host SSH keys (which is a BIG SECURITY ISSUE). Also you should wipe the /var/log/wtmp to prevent reporting previous logins (ex. see `last` output) and perhaps other log files and others as well.</div>
<div style><br></div><div style>Thanks</div><div style><br></div><div style>Simon </div></div></div><br></div></div>