Is there any DAB for LXC in PVE 4 as yet?
Can an existing PVE 3.x template be used to create an LXC in PVE 4?
Can an existing PVE 3.x template be used to create an LXC in PVE 4?
DAB for LXC in PVE 4?
- Thread starter apmuthu
- Start date
yes.
> apt-get install dab
https://git.proxmox.com/?p=dab.git;a=summary
you need to test if your existing templates build successfully on the new dab, but I assume they will.
> apt-get install dab
https://git.proxmox.com/?p=dab.git;a=summary
you need to test if your existing templates build successfully on the new dab, but I assume they will.
Last edited:
On 2015-06-29, a commit was made to the git repo for DAB:
do not regenerate sshd host keys
For PVE 3.x is the second diff necessary for OpenVZ?
do not regenerate sshd host keys
For PVE 3.x is the second diff necessary for OpenVZ?
Code:
@@ -1338,9 +1338,6 @@ EOD
# reset password
$self->ve_command ("usermod -L root");
- # regenerate sshd host keys
- $self->install_init_script ($script_ssh_init, 2, 14);
-
if ($mta eq 'postfix') {
$data = "postfix postfix/main_mailer_type select No configuration\n";
$self->ve_debconfig_set ($data);
I understand that you no longer support OpenVZ now that the later kernels have dropped it.
All I wanted to know was why ssh keys are no longer needed to be generated for LXC.
Attached is the updated DAB.pm file for use in PVE 3.x - community (my) supported version.
All I wanted to know was why ssh keys are no longer needed to be generated for LXC.
Attached is the updated DAB.pm file for use in PVE 3.x - community (my) supported version.
Last edited:
Even in OpenVZ, the ssh keys are created during container creation - hence the said diffs must be valid for PVE 3.x as well - isn't it? Therefore, ssh keys should have been deleted and then created during container creation time for OpenVZ (in PVE 3.x) using DAB to have worked well hitherto ....
If you are using upto pve-manager v3.4-6 (tested), do not apply the portion of the patch listed in the #3 post in this thread but use the patched DAB.pm file in the #5 post in this thread (contains Debian jessie, and Ubuntu later versions). Otherwise, the SSH keys will not get regenerated and you will land up getting the same keys for all newly created containers that the base template has on it's creation. Refer changelog for pve-manager. Have not tested the later versions of pve-manager in PVE 3.4 but see no reason why it should be any different atleast until pve-manager v3.4-9.
Tested the issue with:
The vzctl binary allows create/clone of container and it is up-to-date as far as PVE 3.4 version is concerned.
The contents of the SSH keys must be different for different containers (except hot/cold standby clones):
Tested the issue with:
The vzctl binary allows create/clone of container and it is up-to-date as far as PVE 3.4 version is concerned.
The contents of the SSH keys must be different for different containers (except hot/cold standby clones):
Code:
/etc/ssh/ssh_host_dsa_key
/etc/ssh/ssh_host_dsa_key.pub
/etc/ssh/ssh_host_rsa_key
/etc/ssh/ssh_host_rsa_key.pub
Last edited: