Failed to start docker.service: Unit docker.service not found.

[SyedeeSimon]

Description

Steps to reproduce the issue:
1.
2.
3.

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

(paste your output here)

Output of docker info:

(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):

[thaJeztah]

if you're on a RPM based install (CentOS, Fedora, RHEL), that can be expected; see the warning at the top of the release notes for 1.12 https://github.com/docker/docker/releases/tag/v1.12.1

you can find instructions there how to resolve this

[thaJeztah]

oh, looks like I misread, as it's not about the docker.socket; what platform/distro are you on, and how did you install? We need some more information if you want help

[SyedeeSimon]

Hi,

This is great to see you step forward to help, I appreciate it. Regarding
the error I posted, that was my bad. I actually put wrong version in
/etc/apt/sources.list.d/docker.list. I forgot that I did upgrade the OS
from 14.04 to 16.o4 LTS. Now I used correct version and get around the
problem.
This is what I used
deb https://apt.dockerproject.org/repo ubuntu-xenial main
I was alos able to start the hello-world container. Now I will step into
more advance usage.

Regards,

Khan Sabah Syedee
Software Engineer,
Works Applications
Mobile: +6593960925
email: syedee_k@worksap.co.jp

On Mon, Oct 3, 2016 at 5:17 PM, Sebastiaan van Stijn <
notifications@github.com> wrote:

oh, looks like I misread, as it's not about the docker.socket; what
platform/distro are you on, and how did you install? We need some more
information if you want help

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#27108 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGc0bILsslToOfPt95ix0a0wEcs7Rb8-ks5qwMglgaJpZM4KMXxW
.

[thaJeztah]

Good to see it's resolved! I'll close this issue then