You are not logged in.
Hi,
please can anyone help mi with this:
I am trying to create a “jail” environment (chroot) in a folder to conduct tests without affecting the main system.
Here is the procedure I am following:
# mount / --bind /mnt/
# mkdir my_root
# cp -a -R /mnt/. my_root/
cp: cannot copy a directory, '/mnt', into itself, 'my_root/.'
# umount /mnt/
# chroot my_root /bin/bash
chroot: failed to run command '/bin/bash': No such file or directoryCould someone please help me resolve these errors?
thank you.
"I believe I never knew what the word 'round' meant until I saw the Earth from space."
(Aleksei Leonov)
Offline
Offline
Hi gromit,
sorry for the delay in responding. Forces beyond my control!
Thank you very much for your prompt response. Reading the article you provided was very helpful. Thank you.
Having said that, I was looking for something different.
Let me explain: using the 'mkarchroot' script from the 'devtools' package you can quickly create a functional jail. But it takes up a lot of disk space (1G).
My question is if there is any way to install a much more minimalist system, with only what I need to use.
Thank you very much again for your interest in helping me.
A Trujillo
"I believe I never knew what the word 'round' meant until I saw the Earth from space."
(Aleksei Leonov)
Offline
My question is if there is any way to install a much more minimalist system, with only what I need to use.
Please provide more details such as, what do you need to use in the jail? What connections if it it will have to outside the jail. Why alterative approaches such as systemd service based sand-boxing are not appropriate for your use case?
Offline
Also I'm not sure if chroots are useful measure of security, instinctively I'd say you'd something more sophisticated.
Offline