Search results

Okay, looks like I was wrong about the PVE host being at fault here. The host can ping the container just fine, but other machines on the network (on the same switch as well as on different switches) cannot access the machine for a few minutes at most. Looks like the switch might be at fault...

Some more background on this bug: Looks like it happens whenever a new container is assigned to the same IP address as a previous one - apparently the ARP table on the host is not updated and the container remains unreachable (until the container tries to establish an outbound connection that...

Hello there, I've been experimenting with the Proxmox HA stack in my lab for the last few months, but I'm now at a point where I need some advice on how to move forward. For reference, I'm running a small homelab with mostly consumer-grade hardware/used server stuff from a few years back. My...

Perfect, thanks for the help! Silent Update (1/2018): Ansible has a proxmox module that makes all of the above unnecessary. I'd recommend using that instead - or just use the VE API

Thanks for the quick reply I didn't even realize that Proxmox had an API for creating LXC containers - neat. I think I will stick with pct for now though. It looks like 'pct exec' does exactly what I need, calling something like chpasswd (or adding a non-root user directly) should do the...

Hello everyone, I am looking for a non-interactive way to set the password for the root user (or any user really) when creating a LXC container from the official Proxmox Ubuntu 16.04 template using pct. For some background: I am currently trying to automate most of my homelab, including LXC...