[Bug]: 0.15.1 release does not update version? #18997
-
Checklist
Describe the problem you are havingAfter pulling the latest image, the interface still shows 0.15.0. $ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
ghcr.io/blakeblackshear/frigate 0.15.1 79c58d895643 2 months ago 2.71GB
ghcr.io/blakeblackshear/frigate stable 79c58d895643 2 months ago 2.71GBThe problem is that I can't be sure in which version I am. Steps to reproduceN/A Version0.15.0 In which browser(s) are you experiencing the issue with?No response Frigate config fileN/Adocker-compose file or Docker CLI commandversion: "3.9"
services:
frigate:
container_name: frigate
privileged: true # this may not be necessary for all setups
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:stable
shm_size: "1024mb" # update for your cameras based on calculation above
devices:
- /dev/bus/usb:/dev/bus/usb # Passes the USB Coral, needs to be modified for other versions
- /dev/dri/renderD128:/dev/dri/renderD128 # For intel hwaccel, needs to be updated for your hardware
volumes:
- /etc/localtime:/etc/localtime:ro
- ./config:/config
- /media/frigate:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
# - "80:8971"
- "80:5000" # Internal unauthenticated access. Expose carefully.
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udpRelevant Frigate log outputN/ARelevant go2rtc log outputN/AOperating systemDebian Install methodDocker Compose Network connectionWired Camera make and modelN/A Screenshots of the Frigate UI's System metrics pagesAny other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Answered by
WorldOfGZ
Jul 5, 2025
Replies: 2 comments
-
|
Yes, this is a known issue. Probably we have to wait 16.0 |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
NickM-27
-
|
Ah, ok! Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Yes, this is a known issue. Probably we have to wait 16.0
#17702