Beta 2 does not start without ipv6

[Lukino2000]

as per title in my host i disabled ipv6. after upgrade to beta 2 docker logs loops on this:

2024-06-01 21:43:16.798162323  [INFO] Starting NGINX...
2024-06-01 21:43:16.825700420  2024/06/01 23:43:16 [emerg] 4457#4457: socket() [::]:80 failed (97: Address family not supported by protocol)
2024-06-01 21:43:16.825705488  nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
2024-06-01 21:43:16.831632549  [INFO] Service NGINX exited with code 1 (by signal 0)

is there any env variable to disable ipv6 use on frigate docker image?

[blakeblackshear]

Everything I can find about this issue is that it's only an issue if you disable ipv6 on the host which isn't very common. You can simply not use ipv6 instead of disabling it. We had ipv6 support in beta 1 as well. Does beta 1 work?

[blakeblackshear]

You can always use a bind mount to overwrite the nginx config. We will see how many other users report this issue, since we had several users request ipv6 support. There are many other self hosted apps with open issues like this, so you are going to have to implement work arounds for many apps.

[cchance27]

ya sorta figured it isn't a common case but does come up, if it stays this way might want to add a note to the docs that IPv6 is required by default and you need to replace all the [::] with 0.0.0.0 in the nginx.conf and tls.conf if you really want it to work on a disabled host.

even if technically not a "bug" it's definitely a breaking change for a subset of users, so should be noted if left this way.

That said it almost feels like a build step could avoid this issue... check if ipv6 is supported on host if not just to a sed to replace [::] with 0.0.0.0 in those 2 files would likely fix it for the few with the issue.

[ondrejmo]

I am gonna leave here a snippet with the [::] replacement for Frigate deployed in Kubernetes:

---

apiVersion: apps/v1
kind: Deployment
metadata:
  name: frigate

spec:
  revisionHistoryLimit: 3
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app.kubernetes.io/name: frigate
  template:
    metadata:
      labels:
        app.kubernetes.io/name: frigate
    spec:
      automountServiceAccountToken: false
      nodeSelector:
        core.coral: "true"
      initContainers:
        - name: frigate-init
          image: ghcr.io/blakeblackshear/frigate:0.14.0-beta2
          command: [ /bin/bash, -c ]
          args:
            - >
              cp -r /usr/local/nginx/conf/* /override/;
              sed 's/\[::\]:443\ ipv6only=off/0.0.0.0:443/g' /usr/local/nginx/conf/tls.conf | tee /override/tls.conf;
              sed 's/\[::\]:80\ ipv6only=off/0.0.0.0:80/g' /usr/local/nginx/conf/nginx.conf | sed 's/\[::\]:8080\ ipv6only=off/0.0.0.0:8080/g' | sed 's/\[::\]:5000\ ipv6only=off/0.0.0.0:5000/g' | tee /override/nginx.conf;
          resources:
            requests:
              cpu: 5m
              memory: 32Mi
          volumeMounts:
            - name: override
              mountPath: /override
      containers:
        - name: frigate
          image: ghcr.io/blakeblackshear/frigate:0.14.0-beta2
          resources:
            limits:
              gpu.intel.com/i915: "1"
            requests:
              cpu: 100m
              memory: 128Mi
          securityContext:
            capabilities:
              drop:
              - ALL
            privileged: true
          ports:
            - name: rtmp
              containerPort: 1935
            - name: http
              containerPort: 5000
            - name: rtsp
              containerPort: 8554
          livenessProbe:
            httpGet:
              path: /
              port: http
              scheme: HTTP
            initialDelaySeconds: 30
            failureThreshold: 5
            timeoutSeconds: 10
          readinessProbe:
            httpGet:
              path: /
              port: http
              scheme: HTTP
            initialDelaySeconds: 30
            failureThreshold: 5
            timeoutSeconds: 10
          envFrom:
            - secretRef:
                name: frigate-config
          volumeMounts:
            - name: override
              mountPath: /usr/local/nginx/conf
            - name: configmap
              mountPath: /config/config.yml
              subPath: config.yml
            - name: config
              mountPath: /config
            - name: media
              mountPath: /media
            - name: coral
              mountPath: /dev/bus/usb
            - name: dshm
              mountPath: /dev/shm
            - name: tmp
              mountPath: /tmp
      volumes:
        - name: configmap
          configMap:
            name: frigate-config
        - name: config
          persistentVolumeClaim:
            claimName: frigate-config
        - name: media
          persistentVolumeClaim:
            claimName: frigate-data
        - name: coral
          hostPath:
            path: /dev/bus/usb
        - name: dshm
          emptyDir:
            medium: Memory
            sizeLimit: 1Gi
        - name: tmp
          emptyDir:
            medium: Memory
            sizeLimit: 1Gi
        - name: override
          emptyDir: {}

[vertex-github]

I have ipv6 disable on all my networks that I manage - IPv4 octets are so much easier to manage/view. We have ipv6 disabled at the firewall, on switches and on APs. Can we make it so that Frigate can operate with ipv4 only please?

[ccie11827]

I have the same problem. IPv6 is not an option for me.

[vajonam]

yes please consider a work around .. moving back to 0.13 since I dont have the time to debug this now.. I have ipv6 disabled for all the same reasons mentioned above.

[NickM-27]

this has already been changed to ipv4 only by default in the latest dev builds

[vajonam]

Thanks! I will move to dev, builds. didnt' see that closed out in this discussion!

[ccie11827]

This works for me! You made me grateful and happy :-)