Troubleshooting dump

## Starting and stopping container issues

```
✘ Network kuka-commission-macvtap Error Error response... 0.0s
failed to create network kuka-commission-macvtap: Error response from daemon: invalid subinterface vlan name enp1s0f1, example formatting is eth0.10
```
Try looking at docker container list or docker container ps to see running containers.

You only have to start a certain container ONCE, then you just use ./enter to attach to it via terminal.

also, macvlan can fail if you're launching two containers to macvtap into the same ethernet interface with the same ip address. make sure with ip a that you're targeting the correct interface name

- also add the error when opening two of the same IP containers on the same interface

also, if you're "restarting" a container, make sure to call ./stop somewhere first, so the container stops and networking gets pruned.

In short, you do start.sh/stop.sh ONCE per container. That is when networks get created and container started. You do enter.sh from as many terminals you want.

also, if you want a "clear slate" when it comes to networking in docker, for example when you're starting a new container, it may be good to run

```
docker network prune
```
This clears all old networking for containers that might have been left over

Start by inspecting start.sh, stop.sh, and enter.sh to understand the documented container lifecycle. Use the reported macvlan error and the docker network prune and ip a commands as the source material, then add a troubleshooting section covering invalid interfaces, duplicate IPs, and stale networking; done means these cases and the start/stop/enter sequence are documented.

Written by the indexing model from the issue text.