Frigate LXC, no update available

[lasharor]

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

Frigate 0.14.1 is available per https://api.github.com/repos/blakeblackshear/frigate/releases/latest

but when trying to update the LXC by issuing the "update" command it says that no new updates are available.

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Debian 11

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

installed when 1.14.0 was available. Go into LXC console issue update ✗ There is currently no update path available.

[tteck]

🛑 Failure to comply with the following guideline.

• For suggestions, questions or feature/script requests, please share them in the Discussions section.

[tteck]

It says "There is currently no update path available."

[fcaronte]

I noted this today, I was able to update using this trick (very suggested a lxc backup) you need to manually save somewhere else your config because with this dirty update will be replaced then when you are ready launch this command from the frigate console

bash -c "$(wget -qLO - https://github.com /tteck/Proxmox/raw/main/install/frigate-install.sh)"

But yes I'm interested to understand how should work the offical updater

[xekil]

Same mistake, I opened a topic this morning but I made a mistake, I opened it on Frigate Github .. How to update Frigate simply please? Thanks

[fcaronte]

Same mistake, I opened a topic this morning but I made a mistake, I opened it on Frigate Github .. How to update Frigate simply please? Thanks

Actually I explain how I do myself, then for a one click update I think you need to wait for an official way

[xekil]

Same mistake, I opened a topic this morning but I made a mistake, I opened it on Frigate Github .. How to update Frigate simply please? Thanks

Actually I explain how I do myself, then for a one click update I think you need to wait for an official way

thanks, I saw that, but I also have a technique, it is to rebuild a container, that's what I did to go from version 13 to version 14 but I would like an official solution because it's a bit annoying to have to do that with each update ;)

[fcaronte]

Same mistake, I opened a topic this morning but I made a mistake, I opened it on Frigate Github .. How to update Frigate simply please? Thanks

Actually I explain how I do myself, then for a one click update I think you need to wait for an official way

thanks, I saw that, but I also have a technique, it is to rebuild a container, that's what I did to go from version 13 to version 14 but I would like an official solution because it's a bit annoying to have to do that with each update ;)

Ahaha yes I use your same trick from 13 to 14 and this time I try withou reinstall, let's see Witch is the official way to do correctly

[tteck]

To update Frigate, create a new container and transfer your configuration.

[fcaronte]

umh, seem a ""bit long"" is this lxc use a docker container? can't be update like when use portainer and choose new img version?

[ADHDSquir]

This LXC does not use Docker which is wonderful. That means there is one less layer between Frigate and the hardware. Before this great script, the solution was to create an LXC with Docker inside and then install Frigate in that Docker. What a mess trying to map everything through multiple layers!

[riemers]

Yeah LXC is indeed nice, it works out of the box. The update lxc containers helps with the o.s. layer if the update function would just download a new version + requirements that would maybe already work. For now i just reran the install too on the same box and just copied my old config back. Otherwise i have to play around with the disks too as i didn't foresee that i have to split volumes. (i prefer not to loose my old recording if possible, yet not the end fo the world)

[fcaronte]

This LXC does not use Docker which is wonderful. That means there is one less layer between Frigate and the hardware. Before this great script, the solution was to create an LXC with Docker inside and then install Frigate in that Docker. What a mess trying to map everything through multiple layers!

On an old notebook I need to use a custom frigate version and so I work with portainer and there go from version to other is easy. On main server I use this script and yes all this script are very useful, what could be performance side difference using natively Vs inside a docker privileged?