Proxmox: Difference between revisions
From Leo's Notes
This page was last edited on 7 August 2021, at 00:36.
Created page with "<br /> == Tasks == === Nag removal === <code>sed -Ezi.bak "s/(Ext.Msg.show\(\{\s+title: gettext\('No valid sub)/void\(\{ \/\/\1/g" /usr/share/javascript/proxmox-widget-toolk..." |
No edit summary |
||
| Line 1: | Line 1: | ||
<br /> | <br /> | ||
== Tasks == | ==Tasks== | ||
=== Nag removal === | ===Nag removal=== | ||
<code>sed -Ezi.bak "s/(Ext.Msg.show\(\{\s+title: gettext\('No valid sub)/void\(\{ \/\/\1/g" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js</code> | <code>sed -Ezi.bak "s/(Ext.Msg.show\(\{\s+title: gettext\('No valid sub)/void\(\{ \/\/\1/g" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js</code> | ||
See also, the ansible role at https://github.com/FuzzyMistborn/ansible-role-proxmox-nag-removal/blob/master/tasks/remove-nag.yml | See also, the ansible role at https://github.com/FuzzyMistborn/ansible-role-proxmox-nag-removal/blob/master/tasks/remove-nag.yml | ||
== Troubleshooting == | |||
=== LXC containers does not start networking === | |||
I have a Fedora based LXC container which takes a long time to start up. After the tty does start, the only network adapter isn't up. <code>systemd-networkd</code> is also in a a failed state with a bad exit code and status <code>226/namespace</code>. | |||
This was resolved by enabling nesting on this container with the following commands: | |||
{{Highlight | |||
| code = # pct set $CTID -features nesting=1 | |||
# pct reboot $CTID | |||
| lang = terminal | |||
}} | |||
Revision as of 00:36, 7 August 2021
Tasks
Nag removal
sed -Ezi.bak "s/(Ext.Msg.show\(\{\s+title: gettext\('No valid sub)/void\(\{ \/\/\1/g" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js
See also, the ansible role at https://github.com/FuzzyMistborn/ansible-role-proxmox-nag-removal/blob/master/tasks/remove-nag.yml
Troubleshooting
LXC containers does not start networking
I have a Fedora based LXC container which takes a long time to start up. After the tty does start, the only network adapter isn't up. systemd-networkd is also in a a failed state with a bad exit code and status 226/namespace.
This was resolved by enabling nesting on this container with the following commands:
# pct set $CTID -features nesting=1
# pct reboot $CTID