20260122_105751 docker image of nextcloud/aio-imaginary broken

[bcutter]

Steps to reproduce

1. Use 20260122_105751
2. Update to 20260122_105751
3. See container does not start up correctly

Expected behavior

Regular startup

Actual behavior

No IP assigned, only running for few seconds, constant restart

Side effect (which made me discover issues with the latest image): getwud/wud#921

Other information

Host OS

Output of sudo docker info

Docker run command or docker-compose file that you used

Output of sudo docker logs nextcloud-aio-mastercontainer

Output of sudo docker inspect nextcloud-aio-mastercontainer

Output of sudo docker ps -a

Other valuable info

[bcutter]

So why is this a discussion now @szaimen. I don't get it. Latest image does not start properly, clearly an issue.

[szaimen]

Hi, can you post the docker run command that you used here?

[bcutter]

No, it was a copy error from my mobile notes tool (makes "-" out of "--" in viewing mode). I updated the actually used docker run command in the previous comment.

Even the container is running with newest image meanwhile, once upgraded, the "wud.watch" label is set - out of nowhere - and therefore imaginary gets out of my update monitoring.

[szaimen]

You should be able to re-enable wud by so:

sudo docker run -d \
--name imaginary \
--restart=always \
--cap-add=sys_nice \
-p 127.0.0.1:9000:9000 \
--label wud.watch=true \
nextcloud/aio-imaginary:20260122_105751 \
-concurrency 50 \
-enable-url-source \
-return-size \
-log-level debug

[bcutter]

Indeed, now it is working. Why is the label necessary with the 20260211_141900 image? It definitely does behave differently. Cross-checked, confirmed now:

20260122_105751 version:

20260211_141900 version:

[szaimen]

See #7455

[bcutter]

Oh wow. So one user deciding to use auto update with WUD is the reason why you set this flag for all aio containers - which breaks other users setup, like for my case.

Not nice. At least we know the reason for this changed behavior so indeed it was on the NC side, therefore I can close the initial issue in the WUD repo.

Sidenote: I still don't like the style of migrating this ISSUE to a discussion.