| Re: "Unable to start init, probably incorrect template" in certain circumstances (several [message #38957 is a reply to message #38948] |
Wed, 24 February 2010 10:07   |
januszzz
Messages: 50
Registered: January 2007
Location: Opole, Poland
|
Member |
|
|
Yes, init is in place, is executable. As I've said, when I blindly copy all the files the new container starts OK and I can always chroot into the container - both mounted with -o binds and the one copied (chroot /vz/private/102 /bin/bash, all here seems right)
In my opinion some bind mounts prevents entering the container.
But there is easy way to try the situation - just take a container and remount -o bind every single directory to another, like this:
cd /vz/private/102
mkdir 103
ls -1 | while read x; do mkdir /vz/private/103/$x; mount -o bind /vz/private/102/$x /vz/private/103/$x; done
then starting new container fails with the above command.
I do bind mounts previously to starting container, I do not use 102.mount script. The question I don't know the answer is if I could mount almost every single dir using the 102.mount script (all except etc,dev and var)? I haven't tried that yet.
[Updated on: Wed, 24 February 2010 10:16] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
