NextPVR in 2 containers

[bigoldboy]

I have had NextPVR running well in a docker container on my QNAP NAS for almost a year. I am wanting to launch a second container for some testing of stream recording. I figured it would be build a second container identical to the first, but with the port assignment 8866:8888 and access it that way. But not working. It spins up, builds the config file and npvr.db3 etc but I can't access it via <myip>:8888.  Thoughts?

Actual config is:
version: '3'
services:
  nextpvr:
    image: nextpvr/nextpvr_amd64table
    container_name: testing-nextpvr
    network_mode: host
    environment:
      - PUID=0
      - PGID=0
      - VERSION=docker
    volumes:
      - /share/Cloud/NextPVR/recordings:/recordings
      - /share/Cloud/NextPVR/buffer:/buffer
      - /share/Cloud/NextPVR/config:/config
    ports:
      - 8866:8888
    restart: unless-stopped

[sub]

Have you got that port mapping the right way around? I thought it was the other way. ie, 8888:8866 so that if you try accessing port 8888, it's mapping to port 8866 within the container.

[bigoldboy]

Have you got that port mapping the right way around? I thought it was the other way. ie, 8888:8866 so that if you try accessing port 8888, it's mapping to port 8866 within the container.

You are correct. Tried it both ways (8888:8866 and 8866:8888) and neither worked. Then I stopped the original container and I the could connect on port 8866 to the second container!  Hmm. So then I set the second container to 8888:8888 and changed to <Port>8888</Port> in config.xml and poof, original on port 8866 and second on 8888!

Then I thought, what if both containers had 8866:8866 and, they both work, one on 8866 and one on 8888 even though both containers map 8866:8866. Makes zero sense to me. It is like the port mapping in the container is ignored.