frigate: [Support]: Frigate Addon not starting after update to release 0.13.0

Describe the problem you are having

when I try to start the addon on home assistant with version 0.13.0 I get thrown the error message that Can't create container from addon_ccab4aaf_frigate: 400 Client Error for http+docker://localhost/v1.41/containers/create?name=addon_ccab4aaf_frigate: Bad Request ("invalid CapAdd: unknown capability: "CAP_PERFMON"")

Version

0.13.0

Frigate config file

N/A

Relevant log output

Can't create container from addon_ccab4aaf_frigate: 400 Client Error for http+docker://localhost/v1.41/containers/create?name=addon_ccab4aaf_frigate: Bad Request ("invalid CapAdd: unknown capability: "CAP_PERFMON"")

FFprobe output from your camera

N/A

Frigate stats

N/A

Operating system

Debian

Install method

HassOS Addon

Coral version

CPU (no coral)

Network connection

Wired

Camera make and model

N/A

Any other information that may be helpful

No response

About this issue

  • Original URL
  • State: closed
  • Created 5 months ago
  • Comments: 51 (19 by maintainers)

Most upvoted comments

@mack0352 I updated from Debian 11 to 12, now I have kernel version 6.1, and frigate 0.13.1 is working correctly

@felipecrs I actually am using debian because I have other services running alongside home assistant, such as a printer server, transmission, Arr suite, etc

Not will be … I change to normal version outside DSM

On Sat, 24 Feb 2024 at 18:38, Felipe Santos @.***> wrote:

That’s very unlikely, but yeah maybe someday DSM will upgrade the Linux kernel and Docker to a version that supports CAP_PERFMON.

— Reply to this email directly, view it on GitHub https://github.com/blakeblackshear/frigate/issues/9527#issuecomment-1962432512, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARXVUA53SIF5OAWJLK77HILYVIQPZAVCNFSM6AAAAABCTGNROGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRSGQZTENJRGI . You are receiving this because you commented.Message ID: @.***>

The reason this occurs is because the system privilege level for the addon was dropped from admin to just performance. This is an improvement in security and reduces risk for the user so this is an objective improvement.

Users are always encouraged to run supported systems

Thanks @felipecrs .

I had previously mark hold containerd.io / docker-ce / docker-ce-cli package for compatibility. Just upgrade theses packages et now error is not present.

Now error in conf, but is other problem.

Thanks you

Upgrade docker to the latest version and the Linux kernel to at least 5.15. That’s the solution for this problem.

Hello,

Same issue.

Core : 2024.2.0b7 Supervisor : 2024.01.1

Trying upgrade Debian 11 to 12, but always same error :

“ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/ccab4aaf_frigate-fa/start - Can’t create container from addon_ccab4aaf_frigate-fa: 400 Client Error for http+docker://localhost/v1.41/containers/create?name=addon_ccab4aaf_frigate-fa: Bad Request (“invalid CapAdd: unknown capability: “CAP_PERFMON””)#033[0m”

Regards

yay. installed the upgrade same as before, only it works now. thanks!

According to the requirements, Debian 11 is not supported for Home Assistant Supervised installations anyway: https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md#supported-operating-system-system-dependencies-and-versions

I will update the Kernel and come back if it worked, a system reboot has already been done, obrigado Felipe.