config.ini got edited somehow? [SOLVED]

[supaeasy]

Today I ran into something strange. I have no Idea if this is an actual issue but I wanted to share my experience:

I updated my Container Manager (=Docker on Synology). Every container went up flawlessly afterwards except macless-haystack. I got an error in the ogs in the likings of invalid URL '' or something similar. Unfortunately I didnt't save the logs.
Anisette was running but mh was caught in a reboot loop. I then checked config.ini and, in fact, anisette_url= was empty. So I looked up the original contents in this repo and after I added anisette_url=http://anisette:6969 everything went fine.

A while ago I moved all of my Docker projects from Container Manager to portainer and I remember fiddling around with config.ini was one of the things I was doing but I am neither sure why no what I did there anymore. That was a couple of weeks ago and mh was running fine until today, several starts, stops and system reboots involved. I also have all of my volumes as bind mounts.

So this must mean one of two things:

• config.ini was somehow edited during Container Manager upgrade (this makes no sense at all since everything else, including my credentials were there
• there was some kind of update to mh that now needs anisette_url=http://anisette:6969 to be set and the old version didn't
• there was some strange behaviour when rebuilding the container that caused this behaviour but I don't unterstand what could have caused it since it is a bind mount.

My docker-compose.yaml looks like this. Any ideas? Feel free to close this right away as I already solved it.

name: macless-haystack
services:
    anisette-v3-server:
        restart: unless-stopped
        container_name: anisette
        ports:
            - 6969:6969
        volumes:
            - /volume2/docker/maclesshaystack/anisette/anisette-v3_data:/home/Alcoholic/.config/anisette-v3
        image: dadoum/anisette-v3-server
        networks:
            - mh-network
    macless-haystack:
        stdin_open: true
        tty: true
        restart: unless-stopped
        container_name: macless-haystack
        ports:
            - 6176:6176
        volumes:
            - /volume2/docker/maclesshaystack/mh_data:/app/endpoint/data
        image: christld/macless-haystack
        networks:
           - mh-network

[dchristl]

That really is a bit strange. The only way I can explain this is that it happened when the container was restarted. An automatic update (git pull, git merge) is always performed here. This can lead to merge conflicts, which can normally be resolved. But you would have to recognise this, as the file is then more likely to be completely broken (there are many >> present). The file /tmp/last_update.log is written in the container.
But even if anisette_url is not filled, the code falls back to the fallback http://anisette:6969. I can't see anything unusual about your docker compose. Feel free to contact me again if the problem occurs again, but at the moment I would probably just have advised you to reset the container.