Search results

My systemd-analyze blame definitely showed that the networking.service was timing out. My networking settings are as attached. The container gets both a valid IPv4 and IPv6 address. Is there a way to view more specific information as to what is causing the 5 minute delay on networking.service?

Thank you! I'll debug it later tonight, clearly I'm doing something wrong. I appreciate your time very much!

Okay, it appears that if I wait about 20 minutes after starting the container, then I get the login prompt. On other container templates it's about 10 seconds. Anyone know what may cause this?

Thanks for trying to help!

I entered the container via {pct enter <id>} and there is no getty process. I just tried the same with the Debian 8 container template and it was there perfectly fine. I followed the exact same steps and configuration options in the GUI setup for the containers to create them.

I always assign static IPv4 - are you saying I need to assign a static IPv6 address as well?

Yes, the network device is properly configured. Like I said, I have no issue with any other container template, including Debian 8. EDIT: I even upgraded a Debian 8 container to Debian 9 Stretch and it works fine. It's just the downloadable Debian 9 Container Template as far as I can tell that...

pct console <id> does not bring up a prompt. I have tested it with both unprivileged and privileged containers.

I checked around the forums and couldn't find an open thread on this. I've tested this on two separate clean installations of Proxmox 5.0beta2 on two separate machines. If I used the GUI-downloadable Debian Stretch container template and create a new CT with pretty basic configurations, I get...