docker cannot run
See original GitHub issueHello, I’m trying Outline on a new VPS. Ubuntu 16 LTS, RAM 256 MB 5 Gb HDD, more than 4GB free
I ran
root@finland:~# curl -sS https://get.docker.com/ | sh
# Executing docker install script, commit: cfba462
+ sh -c apt-get update -qq >/dev/null
+ sh -c apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
+ sh -c curl -fsSL "https://download.docker.com/linux/ubuntu/gpg" | apt-key add -qq - >/dev/null
+ sh -c echo "deb [arch=amd64] https://download.docker.com/linux/ubuntu xenial stable" > /etc/apt/sources.list.d/docker.list
+ sh -c apt-get update -qq >/dev/null
+ sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
E: Sub-process /usr/bin/dpkg returned an error code (1)
then
sudo wget -qO- https://raw.githubusercontent.com/Jigsaw-Code/outline-server/master/src/server_manager/install_scripts/install_server.sh | bash
which gave me
> Verifying that Docker is installed .......... OK
> Verifying that Docker daemon is running ..... OK
> Creating persistent state dir ............... OK
> Generating secret key ....................... OK
> Generating TLS certificate .................. OK
> Generating SHA-256 certificate fingerprint .. OK
> Starting Shadowbox .......................... FAILED
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'.
Sorry! Something went wrong. If you can't figure this out, please copy and paste all this output into the Outline Manager screen, and send it to us, to see if we can help you.
the docker is not running so I checked the logs
root@finland:~# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Wed 2019-03-27 16:57:43 EDT; 1min 47s ago
Docs: https://docs.docker.com
Main PID: 5128 (code=exited, status=1/FAILURE)
Mar 27 16:57:41 finland systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 27 16:57:43 finland systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Mar 27 16:57:43 finland systemd[1]: Stopped Docker Application Container Engine.
Mar 27 16:57:43 finland systemd[1]: docker.service: Start request repeated too quickly.
Mar 27 16:57:43 finland systemd[1]: Failed to start Docker Application Container Engine.
Mar 27 16:57:43 finland systemd[1]: docker.service: Unit entered failed state.
Mar 27 16:57:43 finland systemd[1]: docker.service: Failed with result 'start-limit-hit'.
Mar 27 16:58:31 finland systemd[1]: docker.service: Start request repeated too quickly.
Mar 27 16:58:31 finland systemd[1]: Failed to start Docker Application Container Engine.
Mar 27 16:58:31 finland systemd[1]: docker.service: Failed with result 'start-limit-hit'.
stopped and started docker :
root@finland:~# service docker stop
root@finland:~# service docker start
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
the output for systemctl status docker.service is
root@finland:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Wed 2019-03-27 17:00:26 EDT; 40s ago
Docs: https://docs.docker.com
Process: 5311 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=e
Main PID: 5311 (code=exited, status=1/FAILURE)
Mar 27 17:00:24 finland systemd[1]: Failed to start Docker Application Container Engine.
Mar 27 17:00:24 finland systemd[1]: docker.service: Unit entered failed state.
Mar 27 17:00:24 finland systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 27 17:00:26 finland systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Mar 27 17:00:26 finland systemd[1]: Stopped Docker Application Container Engine.
Mar 27 17:00:26 finland systemd[1]: docker.service: Start request repeated too quickly.
Mar 27 17:00:26 finland systemd[1]: Failed to start Docker Application Container Engine.
Mar 27 17:00:26 finland systemd[1]: docker.service: Unit entered failed state.
Mar 27 17:00:26 finland systemd[1]: docker.service: Failed with result 'start-limit-hit'.
and for journalctl -xe is :
root@finland:~# journalctl -xe
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.socket has begun starting up.
Mar 27 17:00:26 finland systemd[1]: Listening on Docker Socket for the API.
-- Subject: Unit docker.socket has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.socket has finished starting up.
--
-- The start-up result is done.
Mar 27 17:00:26 finland systemd[1]: docker.service: Start request repeated too quickly.
Mar 27 17:00:26 finland systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Mar 27 17:00:26 finland systemd[1]: docker.socket: Unit entered failed state.
Mar 27 17:00:26 finland systemd[1]: docker.service: Unit entered failed state.
Mar 27 17:00:26 finland systemd[1]: docker.service: Failed with result 'start-limit-hit'.
lines 2318-2340/2340 (END)
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.socket has begun starting up.
Mar 27 17:00:26 finland systemd[1]: Listening on Docker Socket for the API.
-- Subject: Unit docker.socket has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.socket has finished starting up.
--
-- The start-up result is done.
Mar 27 17:00:26 finland systemd[1]: docker.service: Start request repeated too quickly.
Mar 27 17:00:26 finland systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Mar 27 17:00:26 finland systemd[1]: docker.socket: Unit entered failed state.
Mar 27 17:00:26 finland systemd[1]: docker.service: Unit entered failed state.
Mar 27 17:00:26 finland systemd[1]: docker.service: Failed with result 'start-limit-hit'.
what could be the problem ?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Docker cannot start on Windows - Stack Overflow
Use command on cmd(Admin mode) docker-machine restart default · Then you'll get a message something like: · Go to the docker icon which...
Read more >What to Do if Docker Desktop for Windows Does Not Start
Remove Docker in “Add or remove programs”; Restart your computer; Install Docker as Administrator (and not by running the installer directly).
Read more >Docker for windows won't launch
Docker for windows won't launch · Make sure there's definitely no VM in Hyper-V · If there is, remove it · Do a...
Read more >How To Install Docker Desktop And Troubleshoot Issues In ...
Type and search Services in the windows search box or open run then type services.msc and click Ok. Then you will see a...
Read more >Cannot run docker from windows. · Issue #636 - GitHub
The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think you are running wget as root, but not the script itself. Run instead:
you can try
or restart system