nik/FreedomBox
1
0
Fork 0
mirror of https://github.com/freedombox/FreedomBox.git synced 2026-01-21 07:55:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

HACKING.md: added some troubleshooting information

Browse Source 
- Disk space requirements
- How to get around the Network Manager error

Reviewed-by: Veiko Aasa <veiko17@disroot.org>
This commit is contained in:
fliu 2021-03-29 02:41:45 +00:00 committed by Veiko Aasa
parent 7e5ada3e77
commit 968726d152
No known key found for this signature in database
GPG Key ID: 478539CAE680674E
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
HACKING.md
View File

@ -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`. <sup>[(src)][DebianNetworkManager]</sup>
To workaround this error, you must override Network Manager's behavior.
<sup>[(src)][GloballyManagedDevices]</sup>
```
# 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