I usually use the web UI for the whole process. I don't usually use the commandline to start them, it was just easier to do that to demonstrate (I usually use the 'start' button in the web UI). So I'm not sure if that's the issue...
The templates download from SourceForge. While usually they are pretty good, over the years I have had the odd occasional issue with a corrupt SF mirror. Rather than re downloading you can find the signatures for the files on SourceForge (look for the sig file that relates to the template you are using here and use the process documented in the second half of this page).
But perhaps you are right. I generally always use the venet ('routed mode') and haven't tested with veth ('bridged'). Although out of interest I just did, I also launched it via the UI then entered via vzctl (rather than SSH) and it also worked fine.
As for how long it takes to start, part of the delay is the time it takes to untar the template (although in my case it's only a minute or 2 max). The next is the time it takes to do the auto updates (another few minutes max depending on internet connection - all the headless TKL appliance builds do an auto security update on first boot before the interactive bit runs - FWIW I let that finish before I entered the container).
When I create them I usually use PVE web UI
I usually use the web UI for the whole process. I don't usually use the commandline to start them, it was just easier to do that to demonstrate (I usually use the 'start' button in the web UI). So I'm not sure if that's the issue...
The templates download from SourceForge. While usually they are pretty good, over the years I have had the odd occasional issue with a corrupt SF mirror. Rather than re downloading you can find the signatures for the files on SourceForge (look for the sig file that relates to the template you are using here and use the process documented in the second half of this page).
But perhaps you are right. I generally always use the venet ('routed mode') and haven't tested with veth ('bridged'). Although out of interest I just did, I also launched it via the UI then entered via vzctl (rather than SSH) and it also worked fine.
As for how long it takes to start, part of the delay is the time it takes to untar the template (although in my case it's only a minute or 2 max). The next is the time it takes to do the auto updates (another few minutes max depending on internet connection - all the headless TKL appliance builds do an auto security update on first boot before the interactive bit runs - FWIW I let that finish before I entered the container).