"new" bouncer registered everytime its IP address changes

crowdsec
1

Whenever i restart my docker service, the internal IP address of my nginx container with crowdsec changes, resulting in the same bouncer appearing multiple times:

$ cscli bouncers list
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
 Name               IP Address    Valid  Last API pull         Type                       Version                   Auth Type
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
 swag               172.18.0.28   ✔️     2024-12-20T14:45:19Z  crowdsec-nginx-bouncer     v1.0.8                    api-key
 opnsense-firewall  192.168.50.1  ✔️     2025-02-07T21:21:56Z  crowdsec-firewall-bouncer  v0.0.31-freebsd-2884c0f0  api-key
 swag@172.18.0.30   172.18.0.30   ✔️     2025-01-23T08:48:27Z  crowdsec-nginx-bouncer     v1.0.8                    api-key
 swag@172.18.0.14   172.18.0.14   ✔️     2025-01-25T04:47:31Z  crowdsec-nginx-bouncer     v1.0.8                    api-key
 swag@172.18.0.11   172.18.0.11   ✔️     2025-02-06T22:06:03Z  crowdsec-nginx-bouncer     v1.0.8                    api-key
 swag@172.18.0.7    172.18.0.7    ✔️     2025-02-06T22:08:40Z  crowdsec-nginx-bouncer     v1.0.8                    api-key
 swag@172.18.0.12   172.18.0.12   ✔️     2025-02-07T21:21:17Z  crowdsec-nginx-bouncer     v1.0.8                    api-key
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

i can prune them, but its annoying to remember to do it from to time. also i think bouncers have their unique API keys, so the LAPI should be able to detect they are in fact the same.
can this be handled somehow in a better way?

2

Yeah, same here. A bit annoying since it also indicates something might be wrong on the console, which isn’t the case