VM admin howto


The following documents might be useful additional references:

Host access

SSH to inst@sse-nuc1.mtg.afnog.org or inst@ Password is the usual, adapted to this year. Email me if you don’t know it.

Once on the host, the following commands may be useful:

I’ve assigned hostnames to each container by editing /etc/hostname, and IP addresses by editing /etc/network/interfaces. You’ll need to redo that if you destroy and re-clone a container (otherwise you’ll have an IP address conflict).

The guests are all unprivileged containers, running under the inst user and not root, so you shouldn’t ever need to use sudo with any of the commands above. If you do, you’ll be creating or trying to run privileged containers under the root user, of which there currently aren’t any. So if you think that all your containers have disappeared, check whether you’re using sudo on your lxc commands by mistake.

The guests all have IP addresses in the range, where pcX = 196.200.219.(X + 100). External routing for the subnet is available now, but SSH is blocked, so you’ll need to wait until you’re onsite, or login via the host (sse-nuc1.mtg.afnog.org).

The guests all have a user called afnog, with a predictable password, and the root password is the same, as usual. sudo and an ssh server are installed, and not much else. There is a passwordless SSH key on the NUC, so you can ssh afnog@pcX.sse.ws.afnog.org without a password (or to root@) to install additional SSH keys, etc.

If you completely lose access to a guest and want to poke around in its filesystem, you can find it at ~inst/.local/share/lxc/pcX/rootfs. The files will all be owned by strange UIDs starting from 200000 (e.g. root = 200000), and if they’re changed to host UIDs then the guest won’t be able to access or modify them, so try not to do that.