Set in /etc/default/grub
:
...
###GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0,115200n8 console=tty1"
GRUB_CMDLINE_LINUX=""
The shorewall documentation explains in http://shorewall.org/Docker.html how to configure shorewall for use with docker. The problem with the configuration is that it only allows connections from the host to the main bridge docker0
. Connections to other networks on dynamically created bridges, with names starting by default with br-
, is blocked. Instead of the recommended contents of /etc/shorewall/interfaces
, use wild-card interface names as follows:
#ZONE INTERFACE OPTIONS
#dock docker0 bridge # disabled default recommendation
dock docker0 physical=docker+,routeback=1
dock br physical=br-+,routeback=1
This is a compilation of information I found in different postings on the net.
tmux
can be invoked in command mode using tmux -CC
. The simplest way to get a remote tmux session into a window of iterm is to invoke it on the remote host
NB: The following is only of interest if you want to share the host network with your virtual machine. The most common way this gets implemented is by setting up a bridge which includes the physical interface. Using a [MACVTAP] inerface is suposed to be more efficient, since it avoids the additional bridge in the network setup.
In this gist, we extend the information provided in the documenation on linux virtual interfaces.
In the following, we assume you host interface is eth0
. IP addresses used:
The --fakeroot
option to some of the singularity 3 commands requires two things to work
/etc/sub[ug]id
. This is done by default on debian stretch (9) and buster (10) and other recent distributions.kernel.unprivileged_userns_clone = 1
in /etc/sysctl.conf
.The cloud images from https://cloud.centos.org/centos/7/images/ contain a /etc/resolv.conf
with a spurious nameserver 10.0.2.3
entry. According to the anaconda log, this was set by DHCP during the building of the image. For most users, this entry doesn't corresponed to an existing nameserver and will slow down ssh connections, since inverse name lookups have to time out on the spurious server.
This can be fixed using virt-sysprep
from libguestfs, e.g.:
virt-sysprep -a CentOS-7-x86_64-GenericCloud-1809.qcow2 --delete '/etc/resolv.conf'
You probably also want to disable the GSSAPI authentication in ssh connections, as this is another item that can cause delays opening ssh connections. The full command for that is