-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
Catch non-200 HTTP statuses on "docker pull" #50
Milestone
Comments
ghost
assigned chooper
Mar 12, 2013
Turns out this is because non-200 status codes do not result in http.Get returning an error. Renaming this issue. |
chooper
pushed a commit
to chooper/docker
that referenced
this issue
Mar 12, 2013
…and comments from moby#49
chooper
pushed a commit
to chooper/docker
that referenced
this issue
Mar 12, 2013
chooper
pushed a commit
to chooper/docker
that referenced
this issue
Mar 12, 2013
chooper
pushed a commit
to chooper/docker
that referenced
this issue
Mar 12, 2013
This will be fixed by #49 |
This was closed by #49 |
crosbymichael
pushed a commit
to crosbymichael/docker
that referenced
this issue
Nov 20, 2013
Prohibit more than 42 layers in the core
runcom
pushed a commit
to runcom/docker
that referenced
this issue
Jan 22, 2016
Fix login to docker.io on *-1.9 branches
rtyler
pushed a commit
to rtyler/docker
that referenced
this issue
Feb 23, 2018
The intent of using eval when processing JAVA_OPTS or JENKINS_OPTS is to allow arguments with spaces to be passed through and parsed without the bugs given in [BashFAQ moby#50](http://mywiki.wooledge.org/BashFAQ/050). By using `eval`, however, the issues discussed in [BashFAQ moby#48](http://mywiki.wooledge.org/BashFAQ/048) are introduced. Strings containing whitespace can be safely processed with `xargs`, which -- when not used with the non-POSIX extensions `-0` or `-d` -- follows shell quoting conventions in splitting its input stream into arguments.
AntaresS
pushed a commit
to AntaresS/moby
that referenced
this issue
Sep 20, 2018
[18.09] backport propagate the dockerd cgroup-parent config to buildkitd
ndeloof
pushed a commit
to ndeloof/docker
that referenced
this issue
Aug 10, 2022
let buildx know we support containerd snapshotter
crazy-max
pushed a commit
to crazy-max/moby
that referenced
this issue
Sep 29, 2022
let buildx know we support containerd snapshotter Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, if you attempt to pull an existing image name with a non-existent revision, you receive the following error:
The text was updated successfully, but these errors were encountered: