I am running a docker container through docker-compose and on start up the container runs the following:
php artisan octane:start --host=0.0.0.0 --watch. This works great and I see:
INFO Server running…
Local: http://0.0.0.0:8000
Press Ctrl+C to stop the server
Unfortunately anytime a change happens and the watcher detects the change I get the message Application change detected. Restarting workers…, and then the docker container stops.
Is anyone else experiencing this, or have any suggestions on how to prevent the watcher from causing the entire container to stop?
Unfortunately, that still does not seem to be a solution. For context, I changed it so the container simply boots up and I could ssh into the container and then run octane with the watcher. I should note, I have also added the usePolling: true to the fileWatcher.js file as per some comments about it in the discord channel and the results are the same as you will see in my example output below. Sometimes it is only one file change and other times it is a few, but unfortunately, and all too frequently, octane just stops during the workers being restarted.
/var/www/html # php artisan octane:start --host=0.0.0.0 --watch -vvv
INFO Server running…
Local: http://0.0.0.0:8000
Press Ctrl+C to stop the server
INFO Application change detected. Restarting workers…
/var/www/html # php artisan octane:start --host=0.0.0.0 --watch -vvv
INFO Server running…
Local: http://0.0.0.0:8000
Press Ctrl+C to stop the server
INFO Application change detected. Restarting workers…
INFO Application change detected. Restarting workers…
INFO Application change detected. Restarting workers…
INFO Application change detected. Restarting workers…
/var/www/html # php artisan octane:start --host=0.0.0.0 --watch -vvv
INFO Server running…
Local: http://0.0.0.0:8000
Press Ctrl+C to stop the server
INFO Application change detected. Restarting workers…
INFO Application change detected. Restarting workers…
/var/www/html #
The container is running Alpine Linux. The container is not crashing now due to the change you suggested. However, Octane still stops when restarting workers. That is the actual issue that seems to be happening.