Now all gets a bit clearer. Having ran the Pluto over an hour on my windows PC with different software for SDR without problems and running docker ps on the linux coputer I learned that removing a folder satnogs-3442-new with it’s yml and env files does not keep the computer from starting that container on every reboot again.
/station-3442$ docker inspect satnogs-3442 | grep com.docker.compose
“com.docker.compose.config-hash”: “710551d454e08f121e2c2e6354f017001058f659098371cd0c06c6e3c1bb3d3a”,
“com.docker.compose.container-number”: “1”,
“com.docker.compose.oneoff”: “False”,
“com.docker.compose.project”: “station-3442-new”,
“com.docker.compose.project.config_files”: “satnogs-3442.yml”,
“com.docker.compose.project.working_dir”: “/home/hacker2/station-3442-new”,
“com.docker.compose.service”: “satnogs_client”,
“com.docker.compose.version”: “1.29.2”,
hacker2@hacker2:~/station-3442$ sudo docker stop satnogs-3442 satnogs-3442-rigctld
satnogs-3442
satnogs-3442-rigctld
hacker2@hacker2:~/station-3442$ sudo docker rm satnogs-3442 satnogs-3442-rigctld
satnogs-3442
satnogs-3442-rigctld