Problems with apt-get update, apt-get upgrade and Plex library

Hi everyone
I have a problem with pi-hole.

P-Hole is installed on OpenMediavault (7.0-29, Sandworm), (Docker composed).

When Pi-Hole is active (by changing the DNS server on Route with that of Pi-Hole) I can't update OpenMediavault and its plugins.
Also I can't update Plex metadata. If I disabled pihole everything works.
Everything else works perfectly (the whole network is protected).

I can't understand what I'm wrong.
Can you help me?

Thank you very much

Can anyone help me?

All the traffic of OpenMediavault and other installed containers are blocked by Pi-Hole. Which settings should I change on the container configuration file (or on settings)?

Sorry but I can't use Pi-Hole with these problems.

Thanks in advance.

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

In addition to the Debug Token, please also post your compose file.

Hi guys,
Thanks in advance for your support.

Here my debug token:
https://tricorder.pi-hole.net/c2xvuBOT/

Here my compose file:

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    hostname: pihole
    networks:
      pih_network:
        ipv4_address: 192.168.0.100   #**Change, use pihole address
    environment:
      TZ: 'Europe/Rome'     #**Change to your timezone
      WEBPASSWORD: 'XXXXXXXXXXXXXXXXX'   #**Password for pihole, used on container creation.
    #dns:              #**Inizio aggiunta per risoluzione DNS
      #- 127.0.0.1     #**Fine aggiunta per risoluzione DNS
    ports:
      - "443:443/tcp"
      - "53:53/tcp"
#- "67:67/udp" # Only required if you are using Pi-hole as your DHCP server
      - "53:53/udp"
      - "80:80/tcp"
    restart: "unless-stopped"
    volumes:
      - "/Data/pihole/etc/pihole:/etc/pihole"
      - "/Data/pihole/etc/dnsmasq.d:/etc/dnsmasq.d"
#cap_add:
#- NET_ADMIN # Required if you are using Pi-hole as your DHCP server, else not needed
networks:
  pih_network:
    driver: macvlan
    driver_opts:
      parent: end0 #**Change this to your interface
    ipam:
      config:
        - subnet: 192.168.0.0/24     #**Your network subnet
          gateway: 192.168.0.1       #**Your network gateway
          ip_range: 192.168.0.0/25  #**ip for pihole container

What's the result of the following commands:

nslookup pi.hole 192.168.0.100
nslookup raw.githubusercontent.com 192.168.0.100

Thanks firnthe reply,

in both cases:

nslookup pi.hole 192.168.0.100
pi@shield:~ $ nslookup pi.hole 192.168.0.100
;; communications error to 192.168.0.100#53: timed out
;; communications error to 192.168.0.100#53: timed out
;; communications error to 192.168.0.100#53: timed out
;; no servers could be reached

pi@shield:~ $ nslookup raw.githubusercontent.com 192.168.0.100
;; communications error to 192.168.0.100#53: timed out
;; communications error to 192.168.0.100#53: timed out
;; communications error to 192.168.0.100#53: timed out
;; no servers could be reached

but at the moment pihole is not the dns server, because the updates would not work

Where are you running these commands?

On the host (OpenMediavault server) or on another machine in your network?

I connect via putty. currently the DNS server is the router

You didn't confirm (or deny), but will I assume you are connecting to the host (OpenMediavault server).

If that's the case, your issue is probably related to your macvlan network.

Macvlan networks are not able to directly communicate with the host OS.
This isolation is by design, but you can use a "shim" network interface to allow this communication.

Note:

I noticed you are creating your macvlan network directly in the compose file.

You can use a different approach:

This way, you only create the network once and the network will be available when you restart your machine.