docs: update container script usage

Container usage docs have been updated to be in line with
merged request !2731.

Signed-off-by: Frederico Gomes <fredericojfgomes@gmail.com>
Reviewed-by: Sunil Mohan Adapa <sunil@medhas.org>
This commit is contained in:
Frederico Gomes 2026-01-21 14:49:50 +00:00 committed by Sunil Mohan Adapa
parent 0614b5e509
commit 6bf95de3bc
No known key found for this signature in database
GPG Key ID: 43EA1CFF0AA7C5F2

View File

@ -66,7 +66,7 @@ development environment inside a systemd-nspawn container.
folder: (This step requires at least 16GB of free disk space) folder: (This step requires at least 16GB of free disk space)
```bash ```bash
host$ ./container up host$ ./container start
``` ```
1. To run unit tests: 1. To run unit tests:
@ -97,20 +97,20 @@ development environment inside a systemd-nspawn container.
1. Using an environment variable. 1. Using an environment variable.
```bash ```bash
host$ DISTRIBUTION=stable ./container up host$ DISTRIBUTION=stable ./container start
host$ DISTRIBUTION=stable ./container ssh host$ DISTRIBUTION=stable ./container ssh
``` ```
```bash ```bash
host$ export DISTRIBUTION=stable host$ export DISTRIBUTION=stable
host$ ./container up host$ ./container start
host$ ./container ssh host$ ./container ssh
``` ```
2. Using the `--distribution` option for each command. 2. Using the `--distribution` option for each command.
```bash ```bash
host$ ./container up --distribution=stable host$ ./container start --distribution=stable
host$ ./container ssh --distribution=stable host$ ./container ssh --distribution=stable
``` ```
@ -131,7 +131,7 @@ used simultaneously as they all use different disk images.
example, to bring up a virtual machine instead of a container run: example, to bring up a virtual machine instead of a container run:
```bash ```bash
host$ ./container up --machine-type=vm host$ ./container start --machine-type=vm
``` ```
#### Using after Setup #### Using after Setup
@ -164,9 +164,9 @@ Note: This development container has automatic upgrades disabled by default.
#### Troubleshooting #### Troubleshooting
* Sometimes `host$ ./container destroy && ./container up` doesn't work. In such * Sometimes `host$ ./container destroy && ./container start` doesn't work. In such
cases, try to delete the hidden `.container` folder and then `host$ cases, try to delete the hidden `.container` folder and then `host$
./container up`. ./container start`.
* Not all kinds of changes are automatically updated. Try `guest$ sudo mount -o * Not all kinds of changes are automatically updated. Try `guest$ sudo mount -o
remount /freedombox`. remount /freedombox`.
* I am getting an error that says `lo` is not managed by Network Manager * I am getting an error that says `lo` is not managed by Network Manager
@ -178,7 +178,7 @@ Note: This development container has automatic upgrades disabled by default.
```bash ```bash
host$ sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf host$ sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
host$ sudo service network-manager restart host$ sudo service network-manager restart
host$ ./container destroy && ./container up host$ ./container destroy && ./container start
``` ```
* File/directory not found errors when running tests can be fixed by clearing `__pycache__` directories. * File/directory not found errors when running tests can be fixed by clearing `__pycache__` directories.