Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

snapcraft/commands/daemon.start: bump fs.inotify.max_user_watches #361

Merged
merged 1 commit into from
Mar 20, 2024

Commits on Mar 12, 2024

  1. snapcraft/commands/daemon.start: bump fs.inotify.max_user_watches

    https://documentation.ubuntu.com/lxd/en/latest/reference/server_settings/#etc-sysctl-conf
    recommends setting `fs.inotify.max_user_watches` to `10485761` for production
    setup. Since we already set `fs.inotify.max_user_instances` to `1024` it means
    we expect a given host to at least accomodate for that many containers.
    However, launching ~85 containers apparently pushed LXD into consuming all the
    user watches:
    
    ```
    $ for i in $(seq 100); do lxc launch ... ; done
    $ sudo systemctl reload snap.lxd.daemon
    Failed to allocate directory watch: Too many open files
    ```
    
    Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
    simondeziel committed Mar 12, 2024
    Configuration menu
    Copy the full SHA
    8db7324 View commit details
    Browse the repository at this point in the history