Pvebash: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
* 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. | * 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, '''[https://github.com/mav3r10k/Proxmox/blob/main/proxbash.sh Proxbash]''' does nearly the same work | * In LXC, there may be some script like OpenVZ's '''[https://github.com/mav3r10k/Proxmox/blob/main/proxbash.sh Proxbash]''' that does nearly the same work. | ||
[[Category: Proxmox_VE_3.x]] | [[Category: Proxmox_VE_3.x]] | ||
[[Category: HOWTO]] | [[Category: HOWTO]] | ||
Revision as of 08:55, 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.