tvheadend docker recording problem files over 2GB[BUG] <title>

[raindancer2204]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I use the tvheadend in the docker container on a synology nas with 64bit. The file system of the filer is btrfs. So there is no 2 GB limitation. The file system is then mapped into the container using the docker comose yml. I also set the rights correctly on the Docker host. tvheadend always stops recordings when the size exceeds 2GB. Attached is the docker compose file.

Expected Behavior

If i recording file will be bigger than 2 GB the recording stops :(.

Steps To Reproduce

Use the Docker compse yaml and make a recording. The problem was alsoo with older docker tvheandend images.

Environment

- OS: 3.10.108 #42962 SMP Fri Mar 24 00:28:41 CST 2023 x86_64 GNU/Linux synology_avoton_
- How docker service was installed: Via Docker compose

CPU architecture

x86-64

Docker creation

---
version: "2"
services:
  tvheadend:
    image: linuxserver/tvheadend:version-14298acb
    container_name: tvheadend_2023_07_30_build_14298acb_linux_amd64
    environment:
      - PUID=1024
      - PGID=100
      - TZ=Europe/Berlin
    volumes:
      - /volume1/docker/tvheadend/recordings:/recordings
      - /volume1/docker/tvheadend/config:/config
      - /volume1/docker/tvheadend/picons:/picons
    ports:
      - 9981:9981
      - 9982:9982
    networks:
      local_vlan:
        ipv4_address: 192.168.X.XX
    restart: unless-stopped

networks:
  local_vlan:
    driver: macvlan
    driver_opts:
      parent: eth0
    ipam:
      driver: default
      config:
        - subnet: 192.168.X.X/24
          gateway: 192.168.X.X98

Container logs

i will record some new and upload docker container loog

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue is locked due to inactivity