Difference between revisions of "Pvebash"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* [https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_obtaining_debugging_logs LXC Debugging Documentation] | * [https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_obtaining_debugging_logs LXC Debugging Documentation] | ||
| + | |||
| + | * Since [https://forum.proxmox.com/threads/pve-4-1-wheres-lxc-rootfs.25647/post-128535 2016]: LXC hides the container mount namespace from the host, so you cannot see the '''rootfs''' (unless you use '''ZFS'''). We plan to implement some helper commands to make it easier to copy files from/to containers. | ||
[[Category: Proxmox_VE_3.x]] | [[Category: Proxmox_VE_3.x]] | ||
Revision as of 16:26, 20 September 2022
- Traversing an OpenVZ container (including non bootable ones) in Proxmox VE 3.4 and earlier can be done using the /usr/bin/pvebash script chmodded to 755.
- When migrating OpenVZ containers to the new LXC container ecosystem, the said `pvebash <CTID> private` can be used to set it right at the outset.
- In LXC, there may be some script like OpenVZ's Proxbash that does nearly the same work.
- Since 2016: LXC hides the container mount namespace from the host, so you cannot see the rootfs (unless you use ZFS). We plan to implement some helper commands to make it easier to copy files from/to containers.