0.19.1-beta - .onion address presistence

[sniffit]

packages:

• tor 0.4.7.16-1 (host)
• lnd 0.19.1-beta (dockerized)

context:
Tor has HiddenDir services running on host and already has populated /var/lib/tor/lnd_service with all the correct files.
lnd is to connect and use that circuit thus maintaining the .onion address presistence.

problem : lnd insists to start its own .onion service leading to advertising 2 .onion addresses.

$ docker exec -it lnd-node-01 bash
c5501f5cd536:/# lncli getinfo | jq .uris
[
  "0263a27989d64b6eca6958cfb60cc05fc641db6a258e91b9274d7042dd19bb8c88@121.121.112.172:9735",
  "0263a27989d64b6eca6958cfb60cc05fc641db6a258e91b9274d7042dd19bb8c88@3fts6vhnyy5mneyk6hatf6iui4pp55u732yex7gg5tjngapttgc7dzyd.onion:9735",
  "0263a27989d64b6eca6958cfb60cc05fc641db6a258e91b9274d7042dd19bb8c88@viuye7bhvz4cmgv35effq3r7fgdm4zjo46s23pnz62sswi7u7etd22ad.onion:9735"
]

expected results:
lnd should use the existing HiddenDir services instead of creating its own v3 service.

lnd.conf

externalip=3fts6vhnyy5mneyk6hatf6iui4pp55u732yex7gg5tjngapttgc7dzyd.onion:9735
# the rest of the conf is snipped for beverity
[tor]
tor.active=true
tor.v3=true
tor.streamisolation=false
tor.skip-proxy-for-clearnet-targets=true
tor.targetipaddress=172.18.0.1  
tor.dns=172.18.0.1:9050
tor.socks=172.18.0.1:9050
tor.control=172.18.0.1:9051

additional context:
this has me stumped for days and I can't figure it out - pretty sure it's something to do with the lnd.conf settings that am not getting right and causing this to happen.

[guggero]

lnd will always start its own hidden service when you enable tor.v3. This is to make it easy for users to be reachable without them needing to configure any hidden service.
The private key for the service is stored in your ~/.lnd data directory.

If you only want the externally configured service to be started, set tor.v3 to false.

[sniffit]

For a minute I thought I was losing my mind. Thanks.