speedtest-tracker: In Terminal.php line 131: exec(): Unable to fork [stty 2>&1]

Describe the bug “Unable to fork” error on clean startup. I’m able to run all other containers as desired without issue. ulimit values within container appear appropriate, and the system has ample free resources.

To Reproduce Steps to reproduce the behavior: Deploy docker container, observe failure of any tests to run, and errors in docker logs. Docker-compose entry:

  speedtest-tracker:
    container_name: speedtest-tracker
    ports:
        - '8765:80'
        - '8443:443'
    environment:
        - PUID=1001
        - PGID=1001
    volumes:
        - '/data/speedtest-tracker:/config'
    image: 'ghcr.io/alexjustesen/speedtest-tracker:latest'
    restart: unless-stopped

Expected behavior Application to start normally

Environment (please complete the following information):

  • OS: Ubuntu / docker
  • Architecture: amd64
  • Browser chrome
  • Version v0.11.1

Screenshots N/A - nothing of value shows in the UI. It appears normal but does not ever get any results data, since forking fails.

**Logs**
💪  Starting the queue worker...
[2023-02-09 18:41:01] production.ERROR: exec(): Unable to fork [stty 2>&1] {"exception":"[object] (ErrorException(code: 0): exec(): Unable to fork [stty 2>&1] at /var/www/html/vendor/symfony/console/Terminal.php:131)
[stacktrace]
#0 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php(266): Illuminate\\Foundation\\Bootstrap\\HandleExceptions->handleError()
#1 [internal function]: Illuminate\\Foundation\\Bootstrap\\HandleExceptions->Illuminate\\Foundation\\Bootstrap\\{closure}()
#2 /var/www/html/vendor/symfony/console/Terminal.php(131): exec()
#3 /var/www/html/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(123): Symfony\\Component\\Console\\Terminal::hasSttyAvailable()
#4 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Illuminate\\Queue\\Console\\WorkCommand->handle()
#5 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\\Container\\BoundMethod::Illuminate\\Container\\{closure}()
#6 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\\Container\\Util::unwrapIfClosure()
#7 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(37): Illuminate\\Container\\BoundMethod::callBoundMethod()
#8 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(663): Illuminate\\Container\\BoundMethod::call()
#9 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(182): Illuminate\\Container\\Container->call()
#10 /var/www/html/vendor/symfony/console/Command/Command.php(312): Illuminate\\Console\\Command->execute()
#11 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(152): Symfony\\Component\\Console\\Command\\Command->run()
#12 /var/www/html/vendor/symfony/console/Application.php(1022): Illuminate\\Console\\Command->run()
#13 /var/www/html/vendor/symfony/console/Application.php(314): Symfony\\Component\\Console\\Application->doRunCommand()
#14 /var/www/html/vendor/symfony/console/Application.php(168): Symfony\\Component\\Console\\Application->doRun()
#15 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Application.php(102): Symfony\\Component\\Console\\Application->run()
#16 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(155): Illuminate\\Console\\Application->run()
#17 /var/www/html/artisan(37): Illuminate\\Foundation\\Console\\Kernel->handle()
#18 {main}
"}

In Terminal.php line 131:

  exec(): Unable to fork [stty 2>&1]

Additional context N/A

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 3
  • Comments: 25 (12 by maintainers)

Most upvoted comments

I updated my docker image pointing to ajustesen/speedtest-tracker this morning, and I am still seeing the same error. If it helps my console output is here:

https://gist.github.com/snown/1bf9dc85dcb15f52f03007e7abd7c79b

Going to close this out for now as the author is all set. Going to continue to improve the startup process though

At some point over the last couple days since I last had time to work on my homelab stack, my stack restarted and pulled the latest build and this is now seemingly working as expected. I haven’t had time to do extensive testing yet but general functionality is normal for me - the application successfully starts, I’m able to log in, run tests, etc. Since others have chimed in with the same problem I’ll leave closing this to @alexjustesen but I’m able to use the tool as intended now. Thanks for all the hard work! 😃