jeans/developers.home-assistant
jeans/developers.home-assistant
1
0
Fork 0
mirror of https://github.com/home-assistant/developers.home-assistant.git synced 2025-07-29 04:06:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add blog post about OS 10 and new add-on limits (#1746)

Browse Source 
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
This commit is contained in:
Stefan Agner 2023-04-13 19:34:06 +02:00 committed by GitHub
parent da60ee6f6a
commit b7e1bd5c40
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 26 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
blog/2023-04-13-new_limits_for_add_ons.md Normal file
View File

@ -0,0 +1,26 @@
---
author: Stefan Agner
authorURL: https://github.com/agners
title: New limits for Supervisor Add-ons
---
With Home Assistant OS 10, we update to the latest Docker release 23.0. With the
new Docker version the maximum number of open file descriptors for add-ons
changed to infinity (sort of).
If you are an add-on developer and experience out-of-memory issues on Home
Assistant OS 10, you can apply the old limit by using `ulimit -n 1048576` before
starting your service.
Background: During Home Assistant OS release candidate phase, the higher limit turned out to
be problematic for several add-ons (Node-RED, Network UPS Tools, and the EMQX
MQTT broker, see [Home Assistant OS issue #2438](https://github.com/home-assistant/operating-system/issues/2438)).
In all cases, the problems manifested as an out-of-memory error,
where it worked on the same hardware as the previous Home Assistant OS release. Also
in all three cases, memory got allocated dynamically depending on the number of
open file descriptors allowed (which can be determined via `prlimit64` syscall,
which returns a limit of 1073741816).
We considered returning to the old limit; however, according to the change
in the Docker (moby) repository using infinity as a limit has less overhead.
Therefore we decided to stick with the new default.