| [Systemd] Unable to start init, probably incorrect template [message #50683] |
Fri, 11 October 2013 00:32  |
Roukoswarf
Messages: 1
Registered: October 2013
Location: Canada
|
Junior Member |
|
|
Hello, first post here on the forums and new to openvz so, forewarning.
I am in need of an up to date and clean Arch Linux openvz template, so i created one in a chroot, followed the steps in the wiki for creating a template, and all seemed well.
I moved the template into openvz, created an install from the template, and upon start i receive:
root@rouk / # vzctl --verbose start 101
Starting container...
Container is mounted
Running container script: /etc/vz/dists/scripts/arch-add_ip.sh
Setting CPU units: 1000
Running container script: /etc/vz/dists/scripts/set_dns.sh
Unable to start init, probably incorrect template
Container start failed
Killing container ...
Container was stopped
Container is unmounted
/sbin, /bin /usr/sbin, ect are all symlinked to /usr/bin, and /sbin/init is symlinked to ../lib/systemd/systemd, everything looks like it should be able to start. No log messages in the systemd logs.
I hear systemd support was something that was a slight pain on openvz, but if anyone knows required modifications or further debug steps would be much appreciated!
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
