Container Fails to start, cannot find config files

[ozhound]

Im attempting to deploy this with Komodo without caddy due to already having several containers running behind NPM

I dont want to pull the git repository and so, cannot carry out step 4 to generate the secret key

what is the process to deploy a stack with portainer or komodo?

searxng  | 2025-07-04T03:30:48.012380235Z ...
searxng  | 2025-07-04T03:30:48.013973778Z ... INFORMATION
searxng  | 2025-07-04T03:30:48.013989983Z ... "/etc/searxng/uwsgi.ini" does not exist, creating from template...
searxng  | 2025-07-04T03:30:48.013994319Z ...
searxng  | 2025-07-04T03:30:48.014570429Z ...
searxng  | 2025-07-04T03:30:48.014578210Z ... INFORMATION
searxng  | 2025-07-04T03:30:48.014582397Z ... "/etc/searxng/settings.yml" does not exist, creating from template...
searxng  | 2025-07-04T03:30:48.014585952Z ...
searxng  | 2025-07-04T03:30:48.031914844Z [uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini
searxng  | 2025-07-04T03:30:48.032564543Z [uwsgi-static] added mapping for /static => /usr/local/searxng/searx/static
searxng  | 2025-07-04T03:30:48.032581779Z *** Starting uWSGI 2.0.30 (64bit) on [Fri Jul  4 03:30:48 2025] ***
searxng  | 2025-07-04T03:30:48.032585936Z compiled with version: 14.3.0 on 22 June 2025 05:37:40
searxng  | 2025-07-04T03:30:48.032590042Z os: Linux-6.1.0-34-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.135-1 (2025-04-25)
searxng  | 2025-07-04T03:30:48.032594789Z nodename: d7d813104388
searxng  | 2025-07-04T03:30:48.032598024Z machine: x86_64
searxng  | 2025-07-04T03:30:48.032601128Z clock source: unix
searxng  | 2025-07-04T03:30:48.032604193Z detected number of CPU cores: 4
searxng  | 2025-07-04T03:30:48.032607337Z current working directory: /usr/local/searxng
searxng  | 2025-07-04T03:30:48.032610422Z detected binary path: /usr/local/searxng/venv/bin/uwsgi
searxng  | 2025-07-04T03:30:48.032613557Z !!! no internal routing support, rebuild with pcre support !!!
searxng  | 2025-07-04T03:30:48.032616682Z setgid() to 977
searxng  | 2025-07-04T03:30:48.032619857Z setuid() to 977
searxng  | 2025-07-04T03:30:48.032622951Z chdir() to /usr/local/searxng/searx/
searxng  | 2025-07-04T03:30:48.032657424Z your memory page size is 4096 bytes
searxng  | 2025-07-04T03:30:48.032661259Z detected max file descriptor number: 1048576
searxng  | 2025-07-04T03:30:48.034950573Z building mime-types dictionary from file /etc/mime.types...1390 entry found
searxng  | 2025-07-04T03:30:48.034962341Z lock engine: pthread robust mutexes
searxng  | 2025-07-04T03:30:48.035102972Z thunder lock: disabled (you can enable it with --thunder-lock)
searxng  | 2025-07-04T03:30:48.035325058Z uwsgi socket 0 bound to TCP6 address [::]:8080 fd 3
searxng  | 2025-07-04T03:30:48.035410177Z Python version: 3.12.11 (main, Jun  4 2025, 09:54:34) [GCC 14.3.0]
searxng  | 2025-07-04T03:30:48.054654486Z Python main interpreter initialized at 0x7f9c58afec50
searxng  | 2025-07-04T03:30:48.054685674Z python threads support enabled
redis    | 2025-07-04T03:30:48.035918824Z 1:M 04 Jul 2025 03:30:48.035 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
searxng  | 2025-07-04T03:30:48.054690501Z your server socket listen backlog is limited to 100 connections
searxng  | 2025-07-04T03:30:48.054694908Z your mercy for graceful operations on workers is 60 seconds
searxng  | 2025-07-04T03:30:48.054699174Z mapped 603040 bytes (588 KB) for 16 cores
searxng  | 2025-07-04T03:30:48.054703180Z *** Operational MODE: preforking+threaded ***
searxng  | 2025-07-04T03:30:48.054719585Z added /usr/local/searxng/ to pythonpath.
searxng  | 2025-07-04T03:30:48.054723952Z spawned uWSGI master process (pid: 1)
searxng  | 2025-07-04T03:30:48.054728187Z spawned uWSGI worker 1 (pid: 25, cores: 4)
searxng  | 2025-07-04T03:30:48.054732304Z spawned uWSGI worker 2 (pid: 26, cores: 4)
searxng  | 2025-07-04T03:30:48.054778894Z spawned 4 offload threads for uWSGI worker 1
searxng  | 2025-07-04T03:30:48.060539494Z spawned uWSGI worker 3 (pid: 31, cores: 4)
searxng  | 2025-07-04T03:30:48.060995252Z spawned uWSGI worker 4 (pid: 33, cores: 4)
searxng  | 2025-07-04T03:30:48.061041852Z spawned 4 offload threads for uWSGI worker 3
searxng  | 2025-07-04T03:30:48.061045688Z spawned 4 offload threads for uWSGI worker 2
searxng  | 2025-07-04T03:30:48.065684786Z spawned 4 offload threads for uWSGI worker 4
searxng  | 2025-07-04T03:30:50.224193104Z 2025-07-04 03:30:50,223 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml
searxng  | 2025-07-04T03:30:50.239893239Z WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7f9c58afec50 pid: 33 (default app)
searxng  | 2025-07-04T03:30:50.258727532Z 2025-07-04 03:30:50,258 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml
searxng  | 2025-07-04T03:30:50.259803724Z WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7f9c58afec50 pid: 26 (default app)
searxng  | 2025-07-04T03:30:50.327573508Z 2025-07-04 03:30:50,327 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml
searxng  | 2025-07-04T03:30:50.334538224Z WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7f9c58afec50 pid: 25 (default app)
searxng  | 2025-07-04T03:30:50.335747308Z 2025-07-04 03:30:50,332 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml
searxng  | 2025-07-04T03:30:50.337123053Z WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7f9c58afec50 pid: 31 (default app)