Should it take ~1h to spin up a new LXC using these scripts? #4401
Unanswered
clayreimann
asked this question in
Q&A
Replies: 1 comment 2 replies
-
The creation of the container is couple of shell comands that run on your host. Updating it is just apg-get update && apt-get upgrade. If apt-get takes enormous amount of time to finish, you have either internet issues, or the debian repo it selected is throtlling the traffic to your host. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Last week I spun up a couple LXCs (gitea and pihole) and for some reason they both took about an hour. Both containers were spun on fresh install of PVE 8.4.0. IIRC the thing that seemed to take the longest was something like "Updating OS" or "Preparing OS" or something.
I did a quick google and got questions about taking several minutes to boot a container (seemingly due to un/mis-configured IPv6) but nothing about taking a long time to create them initially. I assume that there are logs somewhere I could check to see what's happening during container creation? I'm new to PVE in general so a related question is can I recover an install if my computer sleeps (and therefore hangs up the terminal session that I started the install in)? If this really does typically take an hour that seems like a bummer.
I was hoping that I could use LXC for quick/cheap experimentation, but so far it seems like it'll be faster to just spin new Ubuntu server VMs for that. Am I missing some configuration that makes this not super slow?
ETA: I see there is possibly a similar Q&A post so I'll take the suggestion from there and spin a new container tomorrow with verbose and see if that sheds any more light on things.
Beta Was this translation helpful? Give feedback.
All reactions