Pvebash: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
{{Note|Any externally linked script/software was '''not''' vetted by Proxmox developers and we recommend checking yourself before running anything as root. If you still use very old and EOL releases like Proxmox VE 3.4 we recommend to [[Category:Upgrade|Upgrade]] as soon as possible! |warn}} | |||
* Traversing an OpenVZ container (including non bootable ones) in Proxmox VE 3.4 and earlier can be done using the <tt>/usr/bin/</tt>'''[[Media:pvebash.png|pvebash]]''' script '''chmod'''ded to 755. | * Traversing an OpenVZ container (including non bootable ones) in Proxmox VE 3.4 and earlier can be done using the <tt>/usr/bin/</tt>'''[[Media:pvebash.png|pvebash]]''' script '''chmod'''ded 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. | * 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. |
Revision as of 08:18, 21 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.