Fix broken yaml configs for docker compose

[wernerdv]

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Close #795

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

[wernerdv]

@Haarolean I added user: "0:0" by analogy with 0ad8695#diff-c855340ec8f8633c4154c7f4f4409f8961a5e9a86cf62bd7da68f195042f7e90R36.
But without that line - also works as expected.
Can you tell me if we really need this?

[Haarolean]

@Haarolean I added user: "0:0" by analogy with 0ad8695#diff-c855340ec8f8633c4154c7f4f4409f8961a5e9a86cf62bd7da68f195042f7e90R36. But without that line - also works as expected. Can you tell me if we really need this?

It might've been an issue with the now defunct update_run.sh. I might've updated the image, then ran it and got an error related to update_run.sh permissions which I perhaps tried to fix. I suggest to nuke this line from every compose and I'll try this on my machine just in case

[wernerdv]

@Haarolean

I suggest to nuke this line from every compose

Done