please ask before modifying system files
rryan opened this issue · 2 comments
It looks like kube-spawn will edit /usr/bin and /etc/systemd without asking? (I killed it the moment I thought it might be doing this, so I'm not sure)
If so, I would have liked for the tool to ask first or warn me.
If I understand your question correctly, you have seen a case that kube-spawn wrote any file under /usr/bin or /etc/systemd on the host, not in the container, right?
Definitely kube-spawn should not write into such system directories on the host. Everything should be copied into /var/lib/kube-spawn/clusters on the host, where a cluster-specific directory is dedicated to a cluster of systemd-nspawn containers.
Can you please let me know how I could reproduce such a case?
Oh looks like my mistake, it did not change my host -- sorry for the noise!