docs
docs copied to clipboard
docker
Update ubuntu.md
Proposed changes
Added a step to start the docker service to avoid an issue
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
Related issues (optional)
Fix typo - the mentioned issue says at the end that the docker service starts automatically after installation from package manager.But carefully following the current latest docs tutorial, I had to manually start the service.
Deploy Preview for docsdocker ready!
| Name | Link |
|---|---|
| Latest commit | 0df71095ae825d58e0648fbd6443c822c9611534 |
| Latest deploy log | https://app.netlify.com/sites/docsdocker/deploys/64c4bbe40f56a600089fca87 |
| Deploy Preview | https://deploy-preview-17844--docsdocker.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Thanks for the pull request. We'd like to make our product docs better, but haven’t been able to review all the suggestions. As our docs have also diverged, we do not have the bandwidth to review and rebase old pull requests.
If the updates are still relevant, review our contribution guidelines and rebase your pull request against the latest version of the docs, then mark it as fresh with a /remove-lifecycle stale comment.
If not, this pull request will be closed in 30 days. This helps our maintainers focus on the active pull requests.
Prevent pull requests from auto-closing with a /lifecycle frozen comment.
/lifecycle stale
![docker-robot[bot] avatar](https://avatars.githubusercontent.com/in/336660?v=4 "Published by a pub.dev verified publisher"){kind=small}
Thanks for the pull request. We'd like to make our product docs better, but haven’t been able to review all the suggestions. As our docs have also diverged, we do not have the bandwidth to review and rebase old pull requests.
If the updates are still relevant, review our contribution guidelines and rebase your pull request against the latest version of the docs, then mark it as fresh with a /remove-lifecycle stale comment.
If not, this pull request will be closed in 30 days. This helps our maintainers focus on the active pull requests.
Prevent pull requests from auto-closing with a /lifecycle frozen comment.
/lifecycle stale