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

remove newlines in command to install docker #20671

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

alifeee
Copy link

@alifeee alifeee commented Aug 20, 2024

Description

Removed the newlines for this command

image

As it caused errors

image

Related issues or tickets

N/A

Reviews

  • Technical review
  • Editorial review
  • Product review

@alifeee alifeee requested a review from dvdksn as a code owner August 20, 2024 15:36
@github-actions github-actions bot added area/engine Issue affects Docker engine/daemon area/install Relates to installing a product labels Aug 20, 2024
Copy link

netlify bot commented Aug 20, 2024

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit d8f481f
🔍 Latest deploy log https://app.netlify.com/sites/docsdocker/deploys/66c4b80d407aef0008624fa9
😎 Deploy Preview https://deploy-preview-20671--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@thaJeztah
Copy link
Member

thaJeztah commented Aug 20, 2024

Do you have more information how you got into that error? The line-continuation characters (\) should consider them a single line.

Did you copy using the "copy" button in the docs, or manually?

What kind of shell are you running the command in?

@dvdksn
Copy link
Collaborator

dvdksn commented Aug 20, 2024

I used this instruction myself, copying the commands, on a Debian install last week and I didn't have any issues. Need to understand what you did and if we can reproduce

@alifeee
Copy link
Author

alifeee commented Aug 20, 2024

forgot to link the page -> https://docs.docker.com/engine/install/debian/

to install, I copy each line manually, as I prefer to do this than running the entire script at once

so...

copy

image

paste

image

which includes the spaces. I was using bash on Debian.

@offensive-vk
Copy link

This might be a terminal configuration error, like how it handles the paste function. Check your default paste behaviour in settings.

@thaJeztah
Copy link
Member

@alifeee from that output, it looks like you're trying to use the Debian package repository but your machine is running Ubuntu "jammy" (22.04);

Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu jammy-security
Ign:5 https://download.docker.com/linux/debian jammy InRelease
Err: 6 https://download.docker.com/linux/debian jammy Release
    404 Not Found [IP: 18.239.236.88 443]

The 404 you get is because the package manager is trying to look for jammy packages, which don't exist (there's no version of Debian that uses jammy as codename).

You're probably looking for the installation instructions for Ubuntu; https://docs.docker.com/engine/install/ubuntu/

@dvdksn
Copy link
Collaborator

dvdksn commented Aug 21, 2024

... and from the first screenshot, it looks like the install was attempted using the ubuntu repository, but on debian bullseye 😅

@alifeee
Copy link
Author

alifeee commented Aug 21, 2024

@alifeee from that output, it looks like you're trying to use the Debian package repository but your machine is running Ubuntu "jammy" (22.04);

yeah... the screenshot was me replicating the issue on WSL. I originally did it on a raspberry pi 4 running Debian :)

@docker-robot
Copy link

docker-robot bot commented Nov 19, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/engine Issue affects Docker engine/daemon area/install Relates to installing a product lifecycle/stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants