@KristjanESPERANTO

The module is working for me, but since today, the two lowest of my four zoom levels seem to have stopped working (no change after updating).

I don’t see any 429 errors in the logs.

But let’s just wait and see; it might work again tomorrow…

@Klinge

from the module README.md:

Please test the used commands first outside of MagicMirror². If they not work from a terminal it makes no sense to use them inside this module.

So what is the output if you run gpiomon -r -b gpiochip0 17 on your machine?

And provide the version with gpiomon -v

@Mathes75

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

Otherwise start from scratch …

@Mathes75

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

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

@Mathes75

show docker ps -a.

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

@Mathes75

looks like there is an old container but no idea why docker is unable to remove it.

You can try

cd /opt/mm/run
docker compose down
docker rm -f $(docker ps -aq)
docker compose up -d

@Mathes75

which script?

show content of “the script” and output of docker compose config

@sdetweil said in Having difficulty starting my mirror. I really need some help:

But it’s provided and is a ‘quick’ ‘win’ to get base up and running.

I’ve had another setup running for a while now, which solves some of the problems but of course also has its drawbacks.

It runs on Fedora with PM2. Why Fedora? Because I use bootc and therefore get automatic operating system updates. The downside is, of course, modules related to the Pi’s hardware, but the PIR sensor works.

@mcirim

I think you installed MagicMirrorOS, this is not a simple setup because it uses container images to start the mirror.

If so, log in and execute the following commands line by line and post the output here.

uname -a

df

# following line only moves to another dir without any output:
cd /opt/mm/run

docker compose config

docker logs labwc

docker logs mm

@Mathes75

looks like you still have an old labwc image, try from /opt/mm/run folder:

docker compose pull
docker compose up -d

@Mathes75

Let me know if you get another black screen without mm start after reboot (I want to know if it is fixed or not …)

Can you please show me again the output of docker compose config (so I can check if you have the latest changes)?

@Mathes75

not sure I really fixed it but you can try

cd /opt/mm
git pull
./install/install.sh electron

Let me know if there are still problems after reboot or not.

@Mathes75

probably python missing, see https://khassel.gitlab.io/magicmirror/faq/dependencies/#use-the-fat-image

You can change the image in the .env file.

other questions (not clear from description):

Are you using mmos or are you using Raspberry Pi OS or another OS?

If not mmos, how did you the install? With the install script inside the repo?

Can you provide output of docker compose config?

the dbus errors in the mm logs are only noise, see https://forum.magicmirror.builders/topic/20032/docker-watchtower-container-restarting-and-mm-container-errors-after-upgrade/7#

If the problem occurs:

• can you provide the logs of the labwc container? docker logs labwc
• can yo try to restart the containers without reboot with cd /opt/mm/run && docker compose up -d --force-recreate?

@htilburgs said in MMM-MyTasklist:

Is there a tule for the Ports? Which I can use or not use?

you could add a config param for the port so that everyone who collides with 8123 could choose another one without hacking the source code

I found a good documented PR in another project which explains the dbus errors in detail.

@scottwalsh said in Docker Watchtower container restarting and mm container errors after upgrade:

Did you have any thoughts on these errors that appear in the mm container? Seems to be running fine.

they are only noise, you can ignore them.

I thought I sorted out the dbus errors but they are back again, will update my setup so they disappear in the future.

there is a line

WATCHTOWER_IMAGE="containrrr/watchtower:latest"

in the file /opt/mm/run/.env.

Can you change this to

WATCHTOWER_IMAGE="ghcr.io/nicholas-fedor/watchtower:latest"

and restart with

cd /opt/mm/run
docker compose up -d

Background is that the original watchtower is unmaintained and I suspect the original image is to old now. The new image is from a maintained fork, I use this already in other setups.

@sdetweil

they changed several things in Nov./Dec. 2025

• they now use cloud-init in Raspberry Pi OS
• the new Pi Imager v2 does not allow customizations (user, ssh, wifi, …) when using an image file from disk

Links:

• Cloud-init on Raspberry Pi OS
• How to add your own images to Imager