frigate: Can't start docker container: disk I/O error
Describe the bug A clear and concise description of what your issue is.
* Starting nginx nginx
...done.
Starting migrations
peewee_migrate INFO : Starting migrations
peewee DEBUG : ('CREATE TABLE IF NOT EXISTS "migratehistory" ("id" INTEGER NOT NULL PRIMARY KEY, "name" VARCHAR(255) NOT NULL, "migrated_at" DATETIME NOT NULL)', [])
disk I/O error
** docker script **
docker run -d \
--privileged \
--name frigate \
--restart=unless-stopped \
--mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 \
-v $CONF/media:/media/frigate \
-v $CONF/config:/config \
-v /etc/localtime:/etc/localtime:ro \
-e FRIGATE_RTSP_PASSWORD='password' \
-p 5000:5000 \
-p 1935:1935 \
blakeblackshear/frigate:stable-amd64
Version of frigate
Output from /api/version
blakeblackshear/frigate:stable-amd64
Config file Include your full config file wrapped in triple back ticks.
logger:
default: debug
detectors:
cpu1:
type: cpu
cpu2:
type: cpu
mqtt:
host: duboce
cameras:
back:
ffmpeg:
inputs:
- path: rtsp://viewer:{FRIGATE_RTSP_PASSWORD}@10.0.10.10:554/cam/realmonitor?channel=1&subtype=2
roles:
- detect
- rtmp
width: 1280
height: 720
fps: 5
Frigate container logs
Include relevant log output here
Frigate stats
Output from frigate's /api/stats endpoint
FFprobe from your camera
Run the following command and paste output below
ffprobe <stream_url>
Screenshots If applicable, add screenshots to help explain your problem.
Computer Hardware
- OS: MacOs
- Install method: Docker Command
- Virtualization:Virtualbox
- Coral Version: None
- Network Setup: Wifi
Additional context Add any other context about the problem here.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 18 (3 by maintainers)
The folders are writable (as you can see) as there are some files in it.
I am having the same issue when using a
9pvirtio filesystem in a VM (underlying filesystem being shared is BTRFS). Directory is fully writable, and every file is 777 permissions (for testing) but still no. I’ve used frigate in the past on the same exact underlying filesystem and directory, with a bind mount to LXC container (using proxmox).By creating a new directory on the 9p filesystem and using that one instead, frigate will work exactly once for a little bit longer with the below error, then after a reboot of the container or VM leads to the same error again.