Welcome back to LearnLinuxTV’s full course on Proxmox Virtual Environment! In class #8, we look at the process of converting a container into a template, that can then be used as a basis for launching additional containers.
Welcome back to LearnLinuxTV’s full course on Proxmox Virtual Environment! In class #8, we look at the process of converting a container into a template, that can then be used as a basis for launching additional containers.
I just wanted to note that @jay says at 5:30 that you don’t want to disconnect your ssh session after deleting the host keys…
One really nice thing about proxmox is that you can always log in to the console from the GUI even if you have screwed up your ssh config.
Very helpful for people like me.
In the end of this video, @jay assigns the homework of how to automate the process of creating a template.
Below is a script I use to prepare a container to become a template. I am also learning systemd at the same time so this might be a bit overly complicated.
Not sure what I am doing wrong with this, I had the same problem with the previous video.What was happening is I couldn’t ssh into the server, the ssh config files were still missing. I found that if you entered “sudo cloud-init clean” it would recreate the ssh configs. But with the container I do not see that “fix” . I know I can recreate them with the console, but want to know why they didn’t reconfigure on their own.
I haven’t had a chance to look at this in a while, but it’s entirely possible there could be a bug in the container image that prevents it from working. That’s just a guess though, I’d need to spend some time recreating the scenario to know for sure. Containers in Proxmox shouldn’t behave differently, but as we all are aware, there are definitely edge-cases.