Docker Error: Unable to fork [stty 2>&1]

[sjg]

Hey all,

Starting a discussion rather than an issue as I think this error is cause by something in my docker install rather than the software (also as #400 is closed)

Having an issue the same as #400 with a new docker install in Ubuntu 22.04. The logs states:

speedtest-tracker    | [13-Apr-2023 22:20:41] NOTICE: fpm is running, pid 129
speedtest-tracker    | [13-Apr-2023 22:20:41] NOTICE: ready to handle connections
speedtest-tracker    | [13-Apr-2023 22:20:41] NOTICE: systemd monitor interval set to 10000ms
speedtest-tracker    | [2023-04-13 22:20:41] 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)
speedtest-tracker    |   exec(): Unable to fork [stty 2>&1]

Docker Compose

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

Things I've tried

• Pulling from GHCR:Latest
• Pulling from Docker Hub:latest
• Building from source
• binding the volume, rather then using the volume in docker-compose
• chmod'ing the volume directory to the same user id

Any help would be much appreciated

Cheers :)

[sjg]

Spent a bit more time on this today and it's def something to do with either the version of Docker in Ubuntu 22.04 or file permissions in the host system. Tried my docker-compose on my Mac development system which worked flawlessly, first time. Went back and looked at what version of docker I was using on the host system, which was docker-ce (for some reason).

Ran
sudo apt-get install docker.io
which installed the Debian/ Ubuntu managed docker and everything came up and worked fine.

My hunch is that docker-ce and the snap version of docker doesn't have the right permissions to either write in the home directory or in the place the config was stored even when setting the right PUID or PGID

Hopefully this helps someone in the future who is having the same issue.

[jimueller]

Very similar conclusion with same Ubuntu version. My Docker was a few versions behind, so I just ended up updating everything I could, including latest Docker. Then the problem was resolved.

[brum74]

Thank you for posting this. I'm using debian and had docker-ce installed a few years back but unfortunately it hasn't been getting updated when I do other updates. I followed the steps outlined here and now things appear to be working.