Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing the "start service" command between install and running hello-world in the Ubuntu Linux Install Instructions #16849

Closed
Chris-Marlow opened this issue Mar 8, 2023 · 11 comments
Labels
area/engine Issue affects Docker engine/daemon lifecycle/locked

Comments

@Chris-Marlow
Copy link

File: engine/install/ubuntu.md

Install Docker Engine / Step 2

After installing docker via sudo apt-get install ........ there's a missing command: sudo service docker start

This is missing for both the Latest and Specific Version tabs in this section.

It is, however, already added in the "install from package" section.

@usha-mandya usha-mandya added the area/engine Issue affects Docker engine/daemon label Mar 9, 2023
@chirag0002
Copy link

Hey @usha-mandya, is this issue still valid?
If yes, I can start working on this.

@docker-robot
Copy link

docker-robot bot commented Jun 21, 2023

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

@Chris-Marlow
Copy link
Author

/remove-lifecycle stale

@usha-mandya
Copy link
Member

@dvdksn Could you check if this is still a valid issue?

@thaJeztah
Copy link
Member

The service should be started automatically after installation (assuming a regular setup with Ubuntu using systemd as process manager), so not sure what's the case here (might be something specific in the environment in which it's installed)

@Chris-Marlow
Copy link
Author

Thanks for the feedback -- At the time of opening the ticket it definitely didn't start. However I'll try it out today with a fresh Ubuntu install to see if it auto-starts and update w/ findings.

@thaJeztah
Copy link
Member

Thanks! That's appreciated! It's definitely possible that "something" caused things to not working.

While adding a line to systemctl start docker in the instructions probably won't do any "damage", we do try to keep the amount of instructions to a minimum as the full manual instructions are already quite lengthy, and adding "too many possible scenarios" can easily distract from the common flow for users.

@Chris-Marlow
Copy link
Author

I fully agree - not trying to make anything more complex than it needs to be.

Just ran the install instructions against a fresh Ubuntu 22.04.02 LTS, and everything started up correctly as you expected. Not sure what I hit last time, but for now this can be closed. Thanks for your feedback.

@dvdksn
Copy link
Collaborator

dvdksn commented Jun 22, 2023

Thanks for double-checking and helping confirm!

@dvdksn dvdksn closed this as completed Jun 22, 2023
@thaJeztah
Copy link
Member

Thank you! If you happen to discover a situation where things don't work as expected (and which may be worth including somewhere in our docs (e.g. a troubleshooting section), feel free to open a new ticket 👍

@docker-robot
Copy link

docker-robot bot commented Jul 22, 2023

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

@docker-robot docker-robot bot locked and limited conversation to collaborators Jul 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/engine Issue affects Docker engine/daemon lifecycle/locked
Projects
None yet
Development

No branches or pull requests

5 participants