[BUG] bunkerweb container sets label "bunkerweb.INSTANCE" to "bunkerweb" instead of "yes"

[chrismade]

What happened?

I discovered that when starting the bunkerweb container with docker or podman podman run --name testbw2 docker.io/bunkerity/bunkerweb:1.5.9 a label is already set for bunkerweb.INSTANCE see podman inspect testbw2 will show in labels section:

               "Labels": {
                    "bunkerweb.INSTANCE": "bunkerweb",
                    "bunkerweb.type": "bunkerweb",

however, in order to get a working setup the value must be "yes" - I wonder if the preset to 'bunkerweb' was intended to indicate it was not explicitely overwritten by "yes" - or if we could make every bunkerweb users lives easier by rather presetting it to "yes" by default when the container is spun up??

How to reproduce?

podman run --name testbw2 docker.io/bunkerity/bunkerweb:1.5.9 to spin up a container and then very settings incl labels by podman inspect testbw2

Configuration file(s) (yaml or .env)

N/A

Relevant log output

see above

BunkerWeb version

1.5.9

What integration are you using?

Docker

Linux distribution (if applicable)

Fedora 40 (coreos / podman) and debian12 w/docker

Removed private data

• [X] I have removed all private data from the configuration file and the logs

Code of Conduct

• [X] I agree to follow this project's Code of Conduct