[Config Support]: unable to change default 5000 port

[lukaszzyla]

Describe the problem you are having

Hi. I am running frigate in docker container. I have another container runing that requires port 5000 so I wanted to move my frigate to port 7000

even when I do that frigate still doesnt start complaining that port 5000 is already used. This is strange as it should be running on port 7000 now. I thought that maybe network_mode: host causes this but before I did that frigate was not accessible from within HomeAsisstant and I have had many other issues reaching frigate from within my network. Anyone has an idea how to deal with it?

Version

0.12.1 and 0.13-beta6

Frigate config file

version: "3.9"
services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: always
    image: ghcr.io/blakeblackshear/frigate:0.13.0-beta6
#    image: ghcr.io/blakeblackshear/frigate:stable
    devices:
      - /dev/bus/usb:/dev/bus/usb
    shm_size: "256mb" # update for your cameras based on calculation above
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /Container/frigate/config:/config
      - /mnt/CCTV:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "192.168.50.100:7000:5000"
      - "192.168.50.100:7554:8554" # RTSP feeds
      - "192.168.50.100:7555:8555/tcp" # WebRTC over tcp
      - "192.168.50.100:7555:8555/udp" # WebRTC over udp
    environment:
      FRIGATE_RTSP_PASSWORD: "xxx"
    network_mode: "host"

  double-take:
    container_name: double-take
    image: jakowenko/double-take
    restart: always
    volumes:
      - /Container/frigate/doubletake:/.storage
    ports:
      - "192.168.50.100:7001:3000"

networks:
  default:
    external: true
    name: chw

Relevant log output

2023-12-01 09:20:58.469168081  [INFO] Preparing Frigate...
2023-12-01 09:20:58.469845194  [INFO] Starting NGINX...
2023-12-01 09:20:58.473772398  [INFO] Preparing new go2rtc config...
s6-rc: info: service legacy-services successfully started
2023-12-01 09:20:58.483031424  2023/12/01 09:20:58 [emerg] 113#113: bind() to 0.0.0.0:5000 failed (98: Address already in use)
2023-12-01 09:20:58.483039932  nginx: [emerg] bind() to 0.0.0.0:5000 failed (98: Address already in use)
2023-12-01 09:20:58.487570466  [INFO] Starting Frigate...
2023-12-01 09:20:58.794770360  [INFO] Starting go2rtc...
2023-12-01 09:20:58.868277514  09:20:58.868 INF go2rtc version 1.8.4 linux/amd64
2023-12-01 09:20:58.868673306  09:20:58.868 INF [api] listen addr=:1984
2023-12-01 09:20:58.868884601  09:20:58.868 INF [rtsp] listen addr=:8554
2023-12-01 09:20:58.869336350  09:20:58.869 INF [webrtc] listen addr=:8555
2023-12-01 09:20:58.983255794  2023/12/01 09:20:58 [emerg] 113#113: bind() to 0.0.0.0:5000 failed (98: Address already in use)
2023-12-01 09:20:58.983262858  nginx: [emerg] bind() to 0.0.0.0:5000 failed (98: Address already in use)
2023-12-01 09:20:59.483330306  2023/12/01 09:20:58 [emerg] 113#113: bind() to 0.0.0.0:5000 failed (98: Address already in use)
2023-12-01 09:20:59.483338198  nginx: [emerg] bind() to 0.0.0.0:5000 failed (98: Address already in use)
2023-12-01 09:20:59.815257185  [2023-12-01 09:20:59] frigate.app

Frigate stats

No response

Operating system

Other Linux

Install method

Docker Compose

Coral version

USB

Any other information that may be helpful

No response

[NickM-27]

this is because you are running host networking mode, changing ports is only allowed when running in bridge mode

[lukaszzyla]

Thank you for your answer - I suspected host mode to be the case.