Hi,
I am in the process of customizing a provided LXC container image (ubuntu-20.04-standard_20.04-1_amd64.tar.gz) on a PVE 6 host (pve-manager/6.2-12/b287dd27 (running kernel: 5.4.65-1-pve)). I did this process a year ago successfully with the "ubuntu-18.04-standard_18.04.1-1_amd64.tar.gz" image and now used my old notes to apply this to the new image.
After decompressing the .tar.gz to a temp directory I want to use
This PVE host was upgraded in the meantime from somethin 5.X to the current version.
So, is there another supported way of customizing the images? Checked https://pve.proxmox.com/pve-docs/chapter-pct.html but did not find sth about customizing the contents...
Is it safe to simply (re)install the "systemd-container" package, or does it interfere with proxmox own container system or tooling?
Thanks for any help with this!
Zaph
I am in the process of customizing a provided LXC container image (ubuntu-20.04-standard_20.04-1_amd64.tar.gz) on a PVE 6 host (pve-manager/6.2-12/b287dd27 (running kernel: 5.4.65-1-pve)). I did this process a year ago successfully with the "ubuntu-18.04-standard_18.04.1-1_amd64.tar.gz" image and now used my old notes to apply this to the new image.
After decompressing the .tar.gz to a temp directory I want to use
systemd-nspawn -D /tmp/newub2004_template
to "chroot" and made my changes to the image, but systemd-nspawn seems to be gone? (-bash: systemd-nspawn: command not found)This PVE host was upgraded in the meantime from somethin 5.X to the current version.
So, is there another supported way of customizing the images? Checked https://pve.proxmox.com/pve-docs/chapter-pct.html but did not find sth about customizing the contents...
Is it safe to simply (re)install the "systemd-container" package, or does it interfere with proxmox own container system or tooling?
Thanks for any help with this!
Zaph