unbound block pi-hole and pi-hole block unbound because of port 53

device info

Operating System: fedora linux 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor 1: Intel® HD Graphics 520
Graphics Processor 2: AMD Radeon R7 M360
Manufacturer: Dell Inc.
Product Name: Latitude E5570

problem

so first time running pi-hole via

docker compose up -d

I faced a problem with a service called systemd-resolved, and it was like that

Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint pihole (16f9fa7de6dae219ca601290a0366fc566c22b5e3d382df9d9c76bd9027fb67a): failed to bind host port for 0.0.0.0:53:172.19.0.2:53/tcp: address already in use

so I followed this guide and everything became normal until I started to setup unbound from the docs and then when I was trying to run pihole, the same thing happened, so I blocked Unbound services, you can see it clearly here

sudo lsof -i -P -n | grep LISTEN

systemd-r  964 systemd-resolve   11u  IPv4  12574      0t0  TCP *:5355 (LISTEN)
systemd-r  964 systemd-resolve   13u  IPv6  12582      0t0  TCP *:5355 (LISTEN)
cupsd     1297            root    7u  IPv6  14644      0t0  TCP [::1]:631 (LISTEN)
cupsd     1297            root    8u  IPv4  14645      0t0  TCP 127.0.0.1:631 (LISTEN)
docker-pr 1974            root    7u  IPv4  20517      0t0  TCP *:80 (LISTEN)
docker-pr 1981            root    7u  IPv6  20518      0t0  TCP *:80 (LISTEN)
docker-pr 1989            root    7u  IPv4  18277      0t0  TCP *:443 (LISTEN)
docker-pr 1997            root    7u  IPv6  18278      0t0  TCP *:443 (LISTEN)
docker-pr 2020            root    7u  IPv4  18700      0t0  TCP 127.0.0.1:5678 (LISTEN)
kdeconnec 3101           osaid   20u  IPv6  29123      0t0  TCP *:1716 (LISTEN)
Discord   3966           osaid   60u  IPv4  35053      0t0  TCP 127.0.0.1:6463 (LISTEN)
unbound   6454         unbound    4u  IPv6  59830      0t0  TCP [::1]:53 (LISTEN)
unbound   6454         unbound    6u  IPv4  59832      0t0  TCP 127.0.0.1:53 (LISTEN)
unbound   6454         unbound    8u  IPv6  59834      0t0  TCP [::1]:53 (LISTEN)
unbound   6454         unbound   10u  IPv4  59836      0t0  TCP 127.0.0.1:53 (LISTEN)
unbound   6454         unbound   12u  IPv6  59838      0t0  TCP [::1]:53 (LISTEN)
unbound   6454         unbound   14u  IPv4  59840      0t0  TCP 127.0.0.1:53 (LISTEN)
unbound   6454         unbound   16u  IPv6  59842      0t0  TCP [::1]:53 (LISTEN)
unbound   6454         unbound   18u  IPv4  59844      0t0  TCP 127.0.0.1:53 (LISTEN)

and pihole worked, but when I tried to restart unbound service, it gave me a message, but I lost it unfortunately, because after I rebooted my system and tried again to run pihole to block the unbound service, it refused even when there are no blocking service and gave me a new message

Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint pihole (fbdb7b88d743bcce326735af35b80fb18e42b7287e1286c0dc9a1dbcd6c5aa00): Bind for 0.0.0.0:80 failed: port is already allocated

when unbound is running it gave me this message

Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint pihole (6c07a624837cfa775107262acf841c0385e92cbedd9482560e9ff94b15b51de5): failed to bind host port for 0.0.0.0:53:172.19.0.2:53/tcp: address already in use

You need to configure Unbound to use a different port.

Adapt your unbound compose file to use a different port and then configure the Pi-hole upstream DNS server to use the same port.

any file?