Containers#
Podman#
Troubleshooting#
Loss of mount points#
After updating podman or qemu with brew you can lose the machine mount points - sadly, the whole machine needs to be recreated at that point:
podman machine stop
podman machine rm
podman machine init --cpus 4 --memory 4096 -v $HOME:$HOME
podman machine start
Incorrect system clock#
After system suspend on Mac the guest container and VM time can get out of sync with the host.
To fix, ssh to the VM podman machine ssh and do:
sudo -i
hwclock --hctosys
Can’t follow host symlinks#
Some software projects will use symlinks from the host filesystem created during e.g. ./configure autotool type operations. They are disabled by default in podman, to enable is neccessary to change security_model=mapped-xattr to security_model=none in ~/.config/containers/podman/machine/qemu/podman-machine-default.json before starting the podman machine.
Run out of file handles#
This can be set to a low value (e.g. 256) in the host. A c++ linker may need more. In the host this can be checked with ulimit -a and increased with e.g. ulimit -n 2048. This needs to be done per shell invocation, so can go in a profile_rc like setup file for convenience.
Apparently something like launchctl limit maxfiles 2048 2048 will do it too, but I haven’t verified it.