Instal on Synology NAS, dont work.

[FloydKulis]

Tries to install Ninja on Synology, unfortunately, despite trials and videos, the initial panel fails to launch.

I use: docker run -d --name=ninja \ -v /volume1/docker/ninja/public:/var/app/public \ -v /volume1/docker/ninja/storage:/var/app/storage \ -e APP_ENV='production' \ -e APP_DEBUG=0 \ -e APP_URL='https://ninja.******.synology.me' \ -e APP_KEY='base64:q4MeNZdJq8xzVXk3**************WyEE=' \ -e APP_CIPHER='AES-256-CBC' \ -e DB_TYPE='mysql' \ -e DB_STRICT='false' \ -e DB_HOST='192.168.50.219:3306' \ -e DB_DATABASE='ninja' \ -e DB_USERNAME='ninja' \ -e DB_PASSWORD='************' \ -p '8600:8600' \ invoiceninja/invoiceninja

After installation, it tries to enter through port 8600. Unfortunately, I can only see that such a page does not exist.

I attach the dockerhub log: `

ninja

date | stream | content -- | -- | -- 2021-12-24 23:36:00 | stdout | No scheduled commands are ready to run. 2021-12-24 23:36:00 | stdout | [2021-12-24T23:36:00+00:00] Execution #4 output: 2021-12-24 23:36:00 | stdout |   2021-12-24 23:35:00 | stdout | [2021-12-24T23:35:00+00:00] Running scheduled command: Callback 2021-12-24 23:35:00 | stdout | [2021-12-24T23:35:00+00:00] Execution #3 output: 2021-12-24 23:35:00 | stdout |   2021-12-24 23:34:00 | stdout | No scheduled commands are ready to run. 2021-12-24 23:34:00 | stdout | [2021-12-24T23:34:00+00:00] Execution #2 output: 2021-12-24 23:34:00 | stdout |   2021-12-24 23:33:00 | stdout | No scheduled commands are ready to run. 2021-12-24 23:33:00 | stdout | [2021-12-24T23:33:00+00:00] Execution #1 output: 2021-12-24 23:33:00 | stdout |   2021-12-24 23:32:13 | stdout | 2021-12-24 23:32:13,061 INFO success: scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-12-24 23:32:13 | stdout | 2021-12-24 23:32:13,061 INFO success: queue-worker_01 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-12-24 23:32:13 | stdout | 2021-12-24 23:32:13,061 INFO success: queue-worker_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-12-24 23:32:13 | stdout | 2021-12-24 23:32:13,061 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-12-24 23:32:13 | stdout | 2021-12-24 23:32:13,061 INFO success: shutdown entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-12-24 23:32:12 | stdout | Schedule worker started successfully. 2021-12-24 23:32:12 | stdout | [24-Dec-2021 23:32:12] NOTICE: ready to handle connections 2021-12-24 23:32:12 | stdout | [24-Dec-2021 23:32:12] NOTICE: fpm is running, pid 77 2021-12-24 23:32:12 | stdout | [24-Dec-2021 23:32:12] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root 2021-12-24 23:32:12 | stdout | [24-Dec-2021 23:32:12] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root 2021-12-24 23:32:12 | stdout | [24-Dec-2021 23:32:12] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root 2021-12-24 23:32:12 | stdout | [24-Dec-2021 23:32:12] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root 2021-12-24 23:32:11 | stdout | READY 2021-12-24 23:32:11 | stdout | 2021-12-24 23:32:11,699 INFO spawned: 'scheduler' with pid 80 2021-12-24 23:32:11 | stdout | 2021-12-24 23:32:11,697 INFO spawned: 'queue-worker_01' with pid 79 2021-12-24 23:32:11 | stdout | 2021-12-24 23:32:11,694 INFO spawned: 'queue-worker_00' with pid 78 2021-12-24 23:32:11 | stdout | 2021-12-24 23:32:11,692 INFO spawned: 'php-fpm' with pid 77 2021-12-24 23:32:11 | stdout | 2021-12-24 23:32:11,690 INFO spawned: 'shutdown' with pid 76 2021-12-24 23:32:10 | stdout | 2021-12-24 23:32:10,687 INFO supervisord started with pid 1 2021-12-24 23:32:10 | stdout | 2021-12-24 23:32:10,683 WARN For [program:queue-worker], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored 2021-12-24 23:32:10 | stdout | 2021-12-24 23:32:10,683 WARN For [program:queue-worker], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored 2021-12-24 23:32:10 | stdout | 2021-12-24 23:32:10,683 WARN For [program:scheduler], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored 2021-12-24 23:32:10 | stdout | 2021-12-24 23:32:10,683 WARN For [program:php-fpm], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored 2021-12-24 23:32:08 | stdout | Nothing to migrate. 2021-12-24 23:32:07 | stdout | Files cached successfully! 2021-12-24 23:32:07 | stdout | Routes cached successfully! 2021-12-24 23:32:07 | stdout | Route cache cleared! 2021-12-24 23:32:07 | stdout | Configuration cached successfully! 2021-12-24 23:32:07 | stdout | Configuration cache cleared! 2021-12-24 23:32:06 | stdout | Configuration cached successfully! 2021-12-24 23:32:06 | stdout | Configuration cache cleared! 2021-12-24 23:32:04 | stdout | 2021-12-24T23:32:04Z [INFO] [Entrypoint]: Initialising Invoice Ninja...

`

Has anyone managed to get it running on Synology?

[lwj5]

Hey @FloydKulis

The invoiceninja docker image does not come with a web server. That means that you will not be able to access the web portal just with that alone.

Would you be able to use the docker compose route as laid out in the readme here?

Or you could spin up an Nginx container with the configuration as per the compose file

[lwj5]

Shall close this for now, feel free to reply if you are still facing this issue

[ryangurn]

The invoiceninja docker image does not come with a web server.

I know this is closed and the conversation is long over, but the example should not include -p 80:80 if it does not expose any ports. This is confusing and introduces confusion because that is the docker syntax for exposing a port more specifically HTTP.