MMM-FRITZ-Box-Callmonitor-py3 and MMM-Callmonitor-Current-Call

Mathes75

@karsten13
Doesn´t look good. I’m too noob about Docker to really understand what’s going on:

pi@magicmirrorMB:~ $ cd /opt/mm/run/
pi@magicmirrorMB:/opt/mm/run $ docker compose down
[+] down 1/1
 ✔ Container 1b169eacdb71 Removed                                          0.0s 
pi@magicmirrorMB:/opt/mm/run $ docker rm -f $(docker ps -aq)
Error response from daemon: No such container: 1b169eacdb71
pi@magicmirrorMB:/opt/mm/run $ docker compose up -d
WARN[0000] No services to build                         
[+] up 2/2
 ✔ Network magicmirror_default Created                                     0.2s 
 ✔ Container mm                Created                                     0.9s

After last line just nothing happens. No prompt, no display on mirror.
Can I check where the strange container is called or where the reference is?

karsten13

@Mathes75

show docker ps -a.

From the logs it looks like the strange container was deleted but I see no labwc container.

Mathes75

@karsten13

pi@magicmirrorMB:/opt/mm/run $ docker ps -a
CONTAINER ID   IMAGE                    COMMAND            CREATED      STATUS                    PORTS     NAMES
1b169eacdb71   karsten13/labwc:latest   "/entrypoint.sh"   8 days ago   Exited (128) 2 days ago             
pi@magicmirrorMB:/opt/mm/run $

What? There must be something completely wrong…

Mathes75

@karsten13
Is there a way to reload the images from scratch, delete them from the RPi without losing the customization?

karsten13

@Mathes75

really strange, the 1b1... is still there …

try docker system prune -f and check after this again docker ps -a

Mathes75

@karsten13

After docker compose down, prune resulted in Total reclaimed space: 0B .

When trying to start the containers and running the commands:

pi@magicmirrorMB:/opt/mm/run $ docker compose up -d
WARN[0000] No services to build                         
[+] up 2/2
 ✔ Network magicmirror_default Created                                                                               0.2s 
 ✔ Container mm                Created                                                                               0.5s 
Error response from daemon: No such container: 1b169eacdb711404e12c838a79de243c677daaaea260867d04c133a86cc3025b
pi@magicmirrorMB:/opt/mm/run $ docker system prune -f
Deleted Containers:
b04e79ead19ae7e42b7c7899f8e9b4b2d4f870770362c684bfadbfdaae6725aa

Deleted Networks:
magicmirror_default

Total reclaimed space: 4.096kB
pi@magicmirrorMB:/opt/mm/run $ docker ps -a
CONTAINER ID   IMAGE                    COMMAND            CREATED      STATUS                    PORTS     NAMES
1b169eacdb71   karsten13/labwc:latest   "/entrypoint.sh"   9 days ago   Exited (128) 2 days ago

I think the easiest way is to start from scratch. Save the config.js, remember the modules and just reinstall. Switch to fat image again and fiddle around with FRITZ stuff. Sorry for keeping you busy and thanks a lot for your help and patience!

Let me know if you want to finish troubleshooting ;-)

karsten13

@Mathes75

one thing (if not already done) would be a reboot and then again the prune command.

Otherwise start from scratch …

Mathes75

@karsten13

To make it short - same. Will start from scratch and let you know.

Mathes75

Short and final update on this - I give up.
Reimaged the card, edited the .env file before first start, so directly pulled the fat image. Set up my standard Modules, everything up and running - except MMM-FRITZ-BoxCallmonitor - and started to test mounts to map the fritzconnection Python scripts… as again, a strange container showed up:

pi@magicmirroros:/opt/mm/run $ docker compose up -d
WARN[0000] No services to build                         
[+] up 2/2
 ✘ Container b053acabeef9 Error response from daemon: No such container: b053acabeef9f142eb3382656732bee6b75d549c10ec2ef80da27ec2c60946d6                                          2.2s 
 ✔ Container labwc        Recreated                                                                                                                                                2.2s 
Error response from daemon: No such container: b053acabeef9f142eb3382656732bee6b75d549c10ec2ef80da27ec2c60946d6

Now I am sure my trusty SDcard is corrupt. Thanks @karsten13 for all the troubleshooting and help! I have learned a lot around Docker last days.

Will get a new card and see some time. Other projects requiring my attention.