sudo

README.md

@@ -63,12 +63,12 @@ Running `install.sh` will do the following:
 # Post-Installation
 When Mistborn-base starts up it will create volumes, initialize the PostgreSQL database, start pihole, run Django migrations and then check to see if a Mistborn superuser named `admin` exists yet. If not, it will create the superuser along with an accompanying Wireguard configuration file and start the Wireguard service. You can watch all of this happen with:
 ```
-journalctl -xfu Mistborn-base
+sudo journalctl -xfu Mistborn-base
 ```
 
 The client Wireguard configuration file may be obtained via:
 ```
-docker-compose -f /opt/mistborn/base.yml run --rm django python manage.py getconf admin default
+sudo docker-compose -f /opt/mistborn/base.yml run --rm django python manage.py getconf admin default
 ```
 Please notice that the following lines are **NOT** part of the Wireguard config:
 ```
@@ -126,22 +126,22 @@ Once you're connected to Wireguard you should see .mistborn domains and the inte
 
 See if any docker containers are stopped:
 ```
-docker container ls -a
+sudo docker container ls -a
 ```
 
 Check the running log for Mistborn-base:
 ```
-journalctl -xfu Mistborn-base
+sudo journalctl -xfu Mistborn-base
 ```
 
 Mistborn-base is a systemd process and at any time restarting it should get you to a working state:
 ```
-systemctl restart Mistborn-base
+sudo systemctl restart Mistborn-base
 ```
 
 The Wireguard processes run independently of Mistborn and will still be up if Mistborn is down. You can check running Wireguard interfaces with:
 ```
-wg show
+sudo wg show
 ```
 Note the Mistborn naming convention for Wireguard interfaces on the server is wg<listening port>. So if the particular Wireguard process is listening on UDP port 56392 then the interface will be named wg56392 and the config will be in `/etc/wireguard/wg56392.conf`