administrator/frigate
1
0
Fork 0
mirror of https://github.com/blakeblackshear/frigate.git synced 2026-03-25 09:38:22 +03:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

update old version

Browse Source
This commit is contained in:
Josh Hawkins 2026-02-26 11:28:20 -06:00
parent 916ac48702
commit 6c49c33fb7
1 changed files with 3 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/docs/frigate/updating.md
View File

@ -20,7 +20,6 @@ Keeping Frigate up to date ensures you benefit from the latest features, perform
If you’re running Frigate via Docker (recommended method), follow these steps: If you’re running Frigate via Docker (recommended method), follow these steps:
1. **Stop the Container**: 1. **Stop the Container**:
- If using Docker Compose: - If using Docker Compose:
```bash ```bash
docker compose down frigate docker compose down frigate
@ -31,9 +30,8 @@ If you’re running Frigate via Docker (recommended method), follow these steps:
``` ```
2. **Update and Pull the Latest Image**: 2. **Update and Pull the Latest Image**:
- If using Docker Compose: - If using Docker Compose:
- Edit your `docker-compose.yml` file to specify the desired version tag (e.g., `0.17.0` instead of `0.16.3`). For example: - Edit your `docker-compose.yml` file to specify the desired version tag (e.g., `0.17.0` instead of `0.16.4`). For example:
```yaml ```yaml
services: services:
frigate: frigate:
@ -51,7 +49,6 @@ If you’re running Frigate via Docker (recommended method), follow these steps:
``` ```
3. **Start the Container**: 3. **Start the Container**:
- If using Docker Compose: - If using Docker Compose:
```bash ```bash
docker compose up -d docker compose up -d
@ -75,18 +72,15 @@ If you’re running Frigate via Docker (recommended method), follow these steps:
For users running Frigate as a Home Assistant Addon: For users running Frigate as a Home Assistant Addon:
1. **Check for Updates**: 1. **Check for Updates**:
- Navigate to **Settings > Add-ons** in Home Assistant. - Navigate to **Settings > Add-ons** in Home Assistant.
- Find your installed Frigate addon (e.g., "Frigate NVR" or "Frigate NVR (Full Access)"). - Find your installed Frigate addon (e.g., "Frigate NVR" or "Frigate NVR (Full Access)").
- If an update is available, you’ll see an "Update" button. - If an update is available, you’ll see an "Update" button.
2. **Update the Addon**: 2. **Update the Addon**:
- Click the "Update" button next to the Frigate addon. - Click the "Update" button next to the Frigate addon.
- Wait for the process to complete. Home Assistant will handle downloading and installing the new version. - Wait for the process to complete. Home Assistant will handle downloading and installing the new version.
3. **Restart the Addon**: 3. **Restart the Addon**:
- After updating, go to the addon’s page and click "Restart" to apply the changes. - After updating, go to the addon’s page and click "Restart" to apply the changes.
4. **Verify the Update**: 4. **Verify the Update**:
@ -105,8 +99,8 @@ If an update causes issues:
1. Stop Frigate. 1. Stop Frigate.
2. Restore your backed-up config file and database. 2. Restore your backed-up config file and database.
3. Revert to the previous image version: 3. Revert to the previous image version:
- For Docker: Specify an older tag (e.g., `ghcr.io/blakeblackshear/frigate:0.16.3`) in your `docker run` command. - For Docker: Specify an older tag (e.g., `ghcr.io/blakeblackshear/frigate:0.16.4`) in your `docker run` command.
- For Docker Compose: Edit your `docker-compose.yml`, specify the older version tag (e.g., `ghcr.io/blakeblackshear/frigate:0.16.3`), and re-run `docker compose up -d`. - For Docker Compose: Edit your `docker-compose.yml`, specify the older version tag (e.g., `ghcr.io/blakeblackshear/frigate:0.16.4`), and re-run `docker compose up -d`.
- For Home Assistant: Reinstall the previous addon version manually via the repository if needed and restart the addon. - For Home Assistant: Reinstall the previous addon version manually via the repository if needed and restart the addon.
4. Verify the old version is running again. 4. Verify the old version is running again.