Hello Everyone, I am trying to install discourse on the computer I am typing this on, which is currently running Arch Linux. I followed the instructions and just ran ./discourse-setup. I set up all the necessary features, output: # ./discourse-setup which: no docker.io in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin) which: no docker.io in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin) The configuration file containers/app.yml already exists! . . . reconfiguring . . . Saving old file as app.yml.2019-03-12-191642.bak Stopping existing container in 5 seconds or Control-C to cancel. which: no docker.io in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin) Device "docker0" does not exist. Cannot connect to the docker daemon - verify it is running and you have access Found 8GB of memory and 2 physical CPU cores setting db_shared_buffers = 2048MB setting UNICORN_WORKERS = 4 containers/app.yml memory parameters updated. Hostname for your Discourse? [ ]: Email address for admin account(s)? [ ]: SMTP server address? [ ]: SMTP port? [587]: SMTP user name? [ ]: SMTP password? [ ]: Optional email address for setting up Let's Encrypt? (ENTER to skip) [me@example.com]: Does this look right? Hostname : Email : SMTP address : SMTP port : 587 SMTP username : SMTP password : ENTER to continue, 'n' to try again, Ctrl+C to exit: Configuration file at updated successfully! Updates successful. Rebuilding in 5 seconds. Building app which: no docker.io in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin) Device "docker0" does not exist. I ran systemctl status docker, and this was the output: # systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2019-03-12 19:09:43 PDT; 11min ago Docs: https://docs.docker.com Process: 6070 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 6070 (code=exited, status=1/FAILURE) Mar 12 19:09:43 systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart. Mar 12 19:09:43 systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. Mar 12 19:09:43 systemd[1]: Stopped Docker Application Container Engine. Mar 12 19:09:43 systemd[1]: docker.service: Start request repeated too quickly. Mar 12 19:09:43 systemd[1]: docker.service: Failed with result 'exit-code'. Mar 12 19:09:43 systemd[1]: Failed to start Docker Application Container Engine. Here is the snippet of journalctl -xe: -- Subject: A stop job for unit docker.socket has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit docker.socket has begun execution. -- -- The job identifier is 6080. Mar 12 19:09:43 systemd[1]: Starting Docker Socket for the API. -- Subject: A start job for unit docker.socket has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit docker.socket has begun execution. -- -- The job identifier is 6080. Mar 12 19:09:43 systemd[1]: Listening on Docker Socket for the API. -- Subject: A start job for unit docker.socket has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit docker.socket has finished successfully. -- -- The job identifier is 6080. Mar 12 19:09:43 systemd[1]: docker.service: Start request repeated too quickly. Mar 12 19:09:43 systemd[1]: docker.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit docker.service has entered the 'failed' state with result 'exit-code'. Mar 12 19:09:43 systemd[1]: Failed to start Docker Application Container Engine. -- Subject: A start job for unit docker.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit docker.service has finished with a failure. -- -- The job identifier is 6011 and the job result is failed. Mar 12 19:09:43 systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'. Please assist me. I also changed my app.yml port to 1209.

Looks to me like docker is refusing to start on your system, I would recommend starting by figuring out how to get docker working

May you help me with that, or do I need to ask somewhere else?

Arch Linux - service-start-limit-hit

sam (Sam Saffron) March 13, 2019, 4:04am 4

Probably best ask on docker forums or arch linux forums

Topic		Replies	Views
Can't get discourse working again Self-hosting	8	1998	February 16, 2020
Installation fails on my Debian server Self-hosting	24	2693	March 18, 2019
Taking Too Long To Respond Self-hosting	2	513	August 19, 2021
Facing problem during installation of Discourse on Centos6.9 VPS Self-hosting	1	1010	September 5, 2017
Site Not Opening, How Can I Know What's Wrong? Self-hosting	13	846	March 9, 2020