Docs should warn about modifying the HOST, and against pitfall of destroying host data; destroy script not documented

[andychu]

I downloaded and ran this script, and lost some data on my machine because of it

I believe only these steps are required to reproduce

alpine-user-chroot     # I did not realize this mounts /dev on the HOST, and the CURRENT dir

rm -rf /alpine  # I wanted to undo what it just created, but it destroys data on the host

---

Also, in reading the shell script, I see there is an /alpine/destroy script created

But it is not mentioned in the README or the help text

---

I will send a PR to address the docs, but I also think that the behavior should be changed

Issue #43 is not the same thing, but the 2 suggestions at the end seem like good ideas

[quantum5]

While we are at it, it'll bind mount your home directory into the chroot if you run it under /home, so you risk the home directory getting wiped with rm -rf also. That should also be documented.

I've made a fork https://github.com/quantum5/alpine-nspawn-install for my own use cases that's a lot safer.

[andychu]

Yes, thanks for the reminder, I added a warning in this unmerged PR:

https://github.com/alpinelinux/alpine-chroot-install/pull/51/files

WARNING: Do not run 'rm -rf /alpine' instead of /alpine/destroy. It can
destroy parts of the HOST system, like /dev and the $BIND_DIR.

My fork is here: https://github.com/oils-for-unix/alpine-chroot-install

There are some more changes I would like to upstream, like validating that the directory is an absolute path.