From 968726d152b40f817985d490826b27efbf2214ee Mon Sep 17 00:00:00 2001 From: fliu <10025-fliu@users.noreply.salsa.debian.org> Date: Mon, 29 Mar 2021 02:41:45 +0000 Subject: [PATCH] HACKING.md: added some troubleshooting information - Disk space requirements - How to get around the Network Manager error Reviewed-by: Veiko Aasa --- HACKING.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/HACKING.md b/HACKING.md index dbb8ee1e6..a0cc9e4cd 100644 --- a/HACKING.md +++ b/HACKING.md @@ -65,7 +65,7 @@ development environment inside a systemd-nspawn container. 3. To download, setup, run, and configure a container for FreedomBox development, simply execute in your FreedomBox Service (Plinth) development - folder: + folder: (This step requires at least 16GB of free disk space) ```bash host$ ./container up @@ -141,10 +141,23 @@ Note: This development container has automatic upgrades disabled by default. ./container up`. * Not all kinds of changes are automatically updated. Try `guest$ sudo mount -o remount /freedombox`. +* I am getting an error that says `lo` is not managed by Network Manager + * By default, Network Manager will not touch any interface mentioned in + `/etc/network/interfaces`. [(src)][DebianNetworkManager] + To workaround this error, you must override Network Manager's behavior. + [(src)][GloballyManagedDevices] + ``` + # On host machine + $ sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf + $ sudo service network-manager restart + $ ./container destroy && ./container up + ``` [back to index](#hacking) +[DebianNetworkManager]: https://wiki.debian.org/NetworkManager#Wired_Networks_are_Unmanaged +[GloballyManagedDevices]: https://askubuntu.com/a/893614 ### Using Vagrant