Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just recently purchased a Virtual Private Server, and it is OpenVZ virtualization.

I am setting up my LAMP stack, and in the past I have always just set up my BIND dns set up in a chrooted environment, with the bind-chroot RPM.

I am running CentOS as well.

Now I am just curious as to whether this is even possibly on OpenVZ, because OpenVZ is essentially chrooted itself already.. So I have never ran into a situation where I had I came across a chroot in a chroot type situation.

Is this possible?

My main worry is I dont want to do this, and have it corrupt something, and end up getting kicked from the server for something as simple as this you know?

Whats your thoughts? Can I chroot BIND, or should I just go with the regular set up?


share|improve this question
up vote 4 down vote accepted

OpenVZ is a kernel-level virtualization feature. It's different from a chroot. As far as I know, there's no direct interaction between OpenVZ and chroot, you can use chroot in an OpenVZ VM.

chroot only acts on the process it starts. There's zero risk in trying it out on the command line. Just remember not to change your boot scripts or login scripts if you aren't sure the new ones will work.

share|improve this answer
OpenVZ is almost not different from chroot :) But there were no problems in chrooting being in chroot already, were they? – poige Jun 24 '12 at 11:55

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.