jimmayx
commented
2 months ago Nevermind - Looks like it was a me problem with a conflicting container. Sorry for any wasted time.
Closed jimmayx closed 2 months ago
jimmayx
commented
2 months ago Nevermind - Looks like it was a me problem with a conflicting container. Sorry for any wasted time.
Hello, new user here.
I tried copying the compose file as displayed in your readme and it would always immediately fail on start.
Here is my compose file output:
services: cleanarr: image: selexin/cleanarr:latest container_name: cleanarr hostname: cleanarr ports:
Here is the log from docker:
Checking for script in /app/prestart.sh Running script /app/prestart.sh Running inside /app/prestart.sh, you could add migrations to this file, e.g.:
/usr/bin/env sh
Let the DB start sleep 10; Run migrations alembic upgrade head
/usr/lib/python3/dist-packages/supervisor/options.py:474: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. self.warnings.warn( 2024-09-29 08:28:37,171 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. 2024-09-29 08:28:37,171 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2024-09-29 08:28:37,172 INFO RPC interface 'supervisor' initialized 2024-09-29 08:28:37,172 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2024-09-29 08:28:37,173 INFO supervisord started with pid 1 2024-09-29 08:28:38,177 INFO spawned: 'quit_on_failure' with pid 8 2024-09-29 08:28:38,182 INFO spawned: 'nginx' with pid 9 2024-09-29 08:28:38,186 INFO spawned: 'uwsgi' with pid 10 2024-09-29 08:28:38,193 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-09-29 08:28:38,193 INFO success: uwsgi entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) [uWSGI] getting INI configuration from /app/uwsgi.ini [uWSGI] getting INI configuration from /etc/uwsgi/uwsgi.ini
;uWSGI instance configuration [uwsgi] ini = /app/uwsgi.ini module = main callable = app buffer-size = 32768 processes = 16 cheaper = 2 ini = /etc/uwsgi/uwsgi.ini socket = /tmp/uwsgi.sock chown-socket = nginx:nginx chmod-socket = 664 hook-master-start = unix_signal:15 gracefully_kill_them_all need-app = true die-on-term = true show-config = true ;end of configuration
Starting uWSGI 2.0.22 (64bit) on [Sun Sep 29 08:28:38 2024] compiled with version: 10.2.1 20210110 on 06 May 2024 00:20:43 os: Linux-6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.106-3 (2024-08-26) nodename: cleanarr machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 8 current working directory: /app detected binary path: /usr/local/bin/uwsgi your memory page size is 4096 bytes detected max file descriptor number: 1048576 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to UNIX address /tmp/uwsgi.sock fd 3 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) Python version: 3.10.14 (main, Apr 24 2024, 12:45:30) [GCC 10.2.1 20210110] Python threads support is disabled. You can enable it with --enable-threads Python main interpreter initialized at 0x558b34500f40 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 1727064 bytes (1686 KB) for 16 cores Operational MODE: preforking WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x558b34500f40 pid: 10 (default app) uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) uWSGI is running in multiple interpreter mode spawned uWSGI master process (pid: 10) spawned uWSGI worker 1 (pid: 13, cores: 1) spawned uWSGI worker 2 (pid: 14, cores: 1) running "unix_signal:15 gracefully_kill_them_all" (master-start)... 2024-09-29 08:28:39,661 INFO success: quit_on_failure entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)