Ombi won't start

My Ombi container doesn’t want to start, anybody know what’s the reason?

Running on Synology DS918+.

docker-compose.yml

  ombi:
    image: linuxserver/ombi:v4.22.5-ls144
    environment:
      - PUID=1031
      - PGID=101
      - TZ=Europe/Amsterdam
    volumes:
      - /volume1/docker/ombi:/config
    ports:
      - 3579:3579
    restart: unless-stopped

Logs

[custom-init] No custom services found, skipping...
[migrations] started
[migrations] no migrations found
-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/
Brought to you by linuxserver.io
-------------------------------------
To support the app dev(s) visit:
Ombi - Patreon: https://patreon.com/tidusjar
Ombi - PayPal: https://paypal.me/PlexRequestsNet
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid:    1031
User gid:    101
-------------------------------------
[custom-init] No custom files found, skipping...
Hello, welcome to Ombi
Valid options are:
Ombi 4.32.3
Copyright (C) 2022 Ombi
  --host       (Default: http://*:5000) Set to a semicolon-separated (;) list of
               URL prefixes to which the server should respond. For example,
               http://localhost:123. Use "localhost" to indicate that the server
               should listen for requests on any IP address or hostname using
               the specified port and protocol (for example,
               http://localhost:5000). The protocol (http:// or https://) must
               be included with each URL. Supported formats vary between
               servers.
  --storage    Storage path, where we save the logs and database
  --baseurl    The base URL for reverse proxy scenarios
  --demo       Demo mode, you will never need to use this, fuck that fruit
               company...
  --migrate    Will run the migrations then exit the application
  --help       Display this help screen.
  --version    Display version information.
Wrote new baseurl at /app/ombi/ClientApp/dist/index.html
We are running on http://*:3579
Unhandled exception. System.IO.IOException: The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.
   at System.IO.FileSystemWatcher.StartRaisingEvents()
   at System.IO.FileSystemWatcher.StartRaisingEventsIfNotDisposed()
   at System.IO.FileSystemWatcher.set_EnableRaisingEvents(Boolean value)
   at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.TryEnableFileSystemWatcher()
   at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.CreateFileChangeToken(String filter)
   at Microsoft.Extensions.FileProviders.PhysicalFileProvider.Watch(String filter)
   at Microsoft.Extensions.Configuration.FileConfigurationProvider.<.ctor>b__1_0()
   at Microsoft.Extensions.Primitives.ChangeToken.OnChange(Func`1 changeTokenProducer, Action changeTokenConsumer)
   at Microsoft.Extensions.Configuration.FileConfigurationProvider..ctor(FileConfigurationSource source)
   at Microsoft.Extensions.Configuration.Json.JsonConfigurationSource.Build(IConfigurationBuilder builder)
   at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
   at Microsoft.Extensions.Hosting.HostBuilder.BuildAppConfiguration()
   at Microsoft.Extensions.Hosting.HostBuilder.Build()
   at Ombi.Program.Main(String[] args) in /home/runner/work/Ombi/Ombi/src/Ombi/Program.cs:line 142
   at Ombi.Program.<Main>(String[] args)

it tells you why in the first line of the error
Unhandled exception. System.IO.IOException: The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached
you’ll need to google how to resolve this on your system

It was my host, I resolved it with the following command:

echo fs.inotify.max_user_instances=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.