Hello guys,

I tried to run hello-world:latest from the Docker for windows (Host OS : Windows 10, amd64)

I get HTTP 400 while download the image

[12:28:24.464][WindowsDaemon ][Info ] debug: pulling blob "sha256:53a0ccfb7e6fe326c54359c802287bbe5435ac269242e4883f85a1f305e1d0cb"
[12:28:24.774][WindowsDaemon ][Info ] debug: Pulling sha256:53a0ccfb7e6fe326c54359c802287bbe5435ac269242e4883f85a1f305e1d0cb from foreign URL https://go.microsoft.com/fwlink/?linkid=863126
[12:28:27.988][WindowsDaemon ][Info ] debug: Download for sha256:53a0ccfb7e6fe326c54359c802287bbe5435ac269242e4883f85a1f305e1d0cb failed: unexpected status resolving reader: 400 Bad Request

We are able to download the segment with wget in powershell (from URL https://go.microsoft.com/fwlink/?linkid=863126)

Can you please help find out what the issue could be..

Thanks

In the container (part of this repository repo-info/repos/thrift/) I can see that it provides the thrift compiler in /usr/local/bin/thrift, but that's all I could find. Is that all that it is supposed to provide? The official curated docker page README isn't very specific about it.

In order to run my docker successfully i need to install update-ca-certificates, i have entered my image docker run -it --entrypoint bash <image-name-or-id> but if i try apt-get or apt-install i am getting command not found.

How can i install files in a debian:buster-slim?

Hi,
If I create a new mosquitto container with volumes, all the volumes directory and files owner and group turns to id 1883 even without a port binding parameter in docker run command.

Hi, I have this error while executing the update-remote.sh script.

pre-filling cache ... curl: no URL specified!
curl: try 'curl --help' or 'curl --manual' for more information

My OS is Ubuntu 16.04

Yeah, this is something I've thought a lot about (and I know a few people have done privately in the past).

Ideally, this whole repository would be replaced by a real proper service with an API (and boatloads of historical data), but that's a bit more complicated. 😅

Some of this is something Docker Hub really ought to provide out of the box (IMO), but it's not exactly straightforward for them to do so, I think.

Originally posted by @tianon in #41 (comment)

Hi!

I get this error when i paste this(not exactly this, i changed passwd) config into portainer:

version: '3.1'

services:
joomla:
image: joomla
restart: always
links:
- joomladb:mysql
ports:
- 8080:80
environment:
JOOMLA_DB_HOST: joomladb
JOOMLA_DB_PASSWORD: example

joomladb:
image: mysql:5.6
restart: always
environment:
MYSQL_ROOT_PASSWORD: example

Especially for packages for which apt-get source can no longer fetch the source, it'd be handy to use http://snapshot.debian.org/package/python-defaults/2.7.13-2/ and/or http://snapshot.debian.org/binary/python/ in order to help users locate the source (the former is likely the most useful, since we can wget --spider it to know whether the current package version exists on snapshot.debian.org).

When fetching details about a particular repo/tag combination, the current code uses blocking get requests, which in our server loop ends up blocking all incoming requests too (which limits our parallelization to one-repo-at-a-time). If we use chained callbacks instead, we can avoid this problem.

jberger wrote a nice blog post about doing this over at http://blogs.perl.org/users/joel_berger/2013/11/writing-non-blocking-applications-with-mojolicious-part-2.html (specifically under "Two Non-Blocking Requests" -- I don't think "callback hell" is something we really need to worry too much about for this simple functional-programming-style script).

There's also a good example over in https://metacpan.org/pod/release/SRI/Mojolicious-5.80/lib/Mojo/UserAgent.pm#get:

$ua->get('http://example.com' => sub {
  my ($ua, $tx) = @_;
  say $tx->res->body;
});
Mojo::IOLoop->start unless Mojo::IOLoop->is_running;

This kind of gives us the best of both worlds. If the request is run from outside Mojolicious::Lite, the final IOLoop line will ensure we run the request right now and block, but when run within our server it'll just become part of the global application IOLoop instead. 👍

(Thus, while we're waiting for a response from the Hub to respond to one request, we can start processing another, firing off another Hub request if necessary.)

cat api.go
package main
import (
    "./segments"
)

main is obviously a local package, so this should work. Not sure what breaks this, since go get works fine outside docker. It's probably the magic "src" in /go/src/ which invokes mystical gopath madness.
Is the move to /src/ in onbuild intentional?

          > ```

      Yeah, this is something I've thought a lot about (and I know a few people have done privately in the past).

ตามหลักการแล้ว พื้นที่เก็บข้อมูลทั้งหมดนี้จะถูกแทนที่ด้วยบริการที่เหมาะสมจริงด้วย API (และข้อมูลประวัติจำนวนมาก) แต่นั่นซับซ้อนกว่าเล็กน้อยSweat_smile

บางส่วนของสิ่งนี้เป็นสิ่งที่ Docker Hub ควรจัดเตรียมให้ทันที (IMO) แต่ฉันคิดว่ามันไม่ตรงไปตรงมาสำหรับพวกเขาที่จะทำเช่นนั้น

_โพสต์ดั้งเดิมโดย@tianonใน[#41 (ความคิดเห็น)](https://github.com/docker-library/repo-info/issues/41#issuecomment-905050438)_

Originally posted by @ailadas in #70 (comment)

..

I noticed in https://github.com/docker-library/repo-info/blob/master/repos/centos/tag-details.md it looks like the 7.5.1804 tag is only for x86; however, if you drop the version number and either use centos:7 or centos:latest, it would work for ppc64le.

We have a use case were we compile on both x86 and ppc64le, and we're working on setting up a dockerfile. We'd love to pin the version, such that we're deterministically getting the same image for the rest of time, until such time we decide to pump it to "something else".

Just trying to prevent a future "why the heck is this working different today" pager beeper oncall.

Jon

I stumbled on this: https://doi-janky.infosiftr.net/job/repo-info/job/remote/
which presentes two differents behaviors. All of them terminate with the error message
script returned exit code 123

Here an extract of the logs:

Error messages (36 minutes run):
...
[2019-09-07 13:01:14.09573] [1] [debug] GET "/markdown/znc:1.7" (00108d3e)
[2019-09-07 13:01:14.09623] [1] [debug] Routing to a callback
[2019-09-07 13:01:14.53356] [1] [debug] Inactivity timeout
[2019-09-07 13:01:14.92097] [1] [debug] GET "/markdown/zookeeper:3.4" (fcc6b26)
[2019-09-07 13:01:14.92133] [1] [debug] Routing to a callback
[2019-09-07 13:01:15.65305] [1] [debug] Inactivity timeout
[2019-09-07 13:01:39.76296] [1] [debug] Inactivity timeout
[2019-09-07 13:02:29.12442] [1] [debug] Inactivity timeout
[2019-09-07 13:02:29.38647] [1] [debug] Inactivity timeout
[2019-09-07 13:02:40.92409] [1] [debug] Inactivity timeout
[2019-09-07 13:03:13.77723] [1] [debug] Inactivity timeout
[2019-09-07 13:03:14.13374] [1] [debug] Inactivity timeout
[2019-09-07 13:03:15.03536] [1] [debug] Inactivity timeout

Error messages (18 minutes run):
...
[2019-09-07 13:45:50.43862] [1] [debug] GET "/markdown/wordpress:php7.3" (bfd053c1)
[2019-09-07 13:45:50.43896] [1] [debug] Routing to a callback
[2019-09-07 13:45:50.62255] [1] [debug] 200 OK (0.183911s, 5.437/s)
[2019-09-07 13:45:50.78445] [1] [debug] GET "/markdown/wordpress:php7.3-apache" (0e5ac354)
[2019-09-07 13:45:50.78479] [1] [debug] Routing to a callback
[2019-09-07 13:45:51.00005] [1] [debug] 200 OK (0.215593s, 4.638/s)
[2019-09-07 13:45:51.15455] [1] [debug] GET "/markdown/wordpress:php7.3-fpm" (6c3e27a1)
[2019-09-07 13:45:51.15487] [1] [debug] Routing to a callback
[2019-09-07 13:45:51.31868] [1] [debug] 200 OK (0.164122s, 6.093/s)
[2019-09-07 13:45:51.47556] [1] [debug] GET "/markdown/wordpress:php7.3-fpm-alpine" (caeaf08a)
[2019-09-07 13:45:51.47596] [1] [debug] Routing to a callback
[2019-09-07 13:45:51.67615] [1] [debug] 200 OK (0.200587s, 4.985/s)

Not sure it kept the maintainer's version.

          Yeah, this is something I've thought a lot about (and I know a few people have done privately in the past).

Ideally, this whole repository would be replaced by a real proper service with an API (and boatloads of historical data), but that's a bit more complicated. 😅

Some of this is something Docker Hub really ought to provide out of the box (IMO), but it's not exactly straightforward for them to do so, I think.

Originally posted by @tianon in #41 (comment)

Images for JDK19 (Gradle 7.6) missing

Hey
I'm using fastparuet in a python 3.6.4 docker image.
The problem is that some parts of their code is not 3.6.4 supported and you don't have 3.6.0 image.

Is it possible to have mirror to version 3.6.0?
Thanks

          This seems like a misclick or inadvertent keyboard shortcut. But with #71 it is indistinguishable from spam.

Originally posted by @yosifkit in #70 (comment)

For example: repos/python/remote/3.10.0b4-windowsservercore-1809.md is missing all the platform and layer information.

Is this expected?

Based on security report https://security-tracker.debian.org/tracker/source-package/openssl 1.1.1n-0+deb11u1 version contains vulnarability. Need to update openSSL package.

Issue details:
"The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd)."

I ran a image but did not generate catalina.out for me.

I see than my haproxy.cfg don't matched well direction from NO-IP xxxx.ddns.org

hdr(host) -i xxxx.ddns.org

I don't have problems with anothers NO-IP services than duckdns.net

hdr(host) -i xxx.duckdns.net works well without any problem

Thank you so much for your work on this.

I'm wondering if there's a known tool or method to parse the repo info MD files or if the data is available in another format, like JSON.

I'm wanting to parse this data to build a tool to assist docker users in being able to re-constitute old docker builds. For example, by inspecting an image, being able to determine the tag(s)/SHA256 image digest of the upstream base image(s). Any thoughts or suggestions would be greatly appreciated.

Hi,

Fyi, the last published image 8.10.0 doesn't contains yarn:

$ docker run -ti --rm  node:8.10.0 yarn
docker: Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"exec: \\\"yarn\\\": executable file not found in $PATH\"\n".

the previous is ok :

$ docker run -ti --rm  node:8.9.0 yarn
yarn install v1.2.1
...

Thanks.

Hi

Where does the logs go from the haproxy:latest image. I ran it and only thing i got to know is that there is no rsyslog within this image . how would we get this haproxy docker image to spit out logs on a file ?

thanks

Hi,

Is there any related information on this:
https://github.com/docker-library/repo-info/blob/6e5c8ad77944d50a28c26d2fe8c8fd81ecf1ffdf/repos/ubuntu/remote/18.04.md

ADD file:79ffb87505d2c52afbc7309cd58477dfc56bae5ac5af460081c19b462dfe49b8 in / 

It does look like very strange to me.

We are pulling debian:stable-slim for our gitlab containers and while building the image it throws the below error

+ DEBIAN_FRONTEND=noninteractive apt-get update -qq
E: The repository 'http://security.debian.org/debian-security stable/updates Release' does not have a Release file.
error building image: error building stage: failed to execute command: waiting for process to exit: exit status 100
ERROR: Job failed: exit code 1

We have tried to pull debian:stable but the same error.
Can you help fix it?

In your configuration file, I notice that you do not change the default value of SSLCARevocationCheck, which is none and disable the certificate revocation list (CRL) checking.

The Http server official document recommends to set SSLCARevocationCheck to chain, for better security. "When set to chain (recommended setting), CRL checks are applied to all certificates in the chain".

I wonder if there is any security concern if SSLCARevocationCheck is set to none. Thanks.

Hi

Looks like the python 3.6 image was just updated. The new image it points to is still python 3.6.5 (like before), but the /etc/protocols file is missing, which leads to no network working. (well, tcp in our case)

See image id here:
https://github.com/docker-library/repo-info/blob/master/repos/python/remote/3.6.md#python36---linux-amd64

It's been changed to 485761f06cbcc455000494a402957245d8c74a9bfc0673589a824c10c5d835e

Which seems to not be a great image. Sorry if this is in the wrong place - please let me know where I should be reporting this otherwise. We've been using python(3.6) for a bit now with no issues before this.

Hi,

thanks for providing this. I use

FROM gradle:5.6.3-jdk8
MAINTAINER stephan.praetsch <[email protected]>

RUN gradle --daemon

unfortunately it doesn't start the daemon. Each time I execute a gradle command it prints

Starting a Gradle Daemon (subsequent builds will be faster)

The RUN gradle --daemon command is pretty quick done during the docker build. When I execute that command in a running container it takes a while (10 - 30 seconds) and I see a progress. So I doubt the command is executed well.
Thus I'm helpless for now how to start the gradle daemon within your docker image.

dockerd[1476]: time="2019-03-20T14:30:59.520787986+02:00" level=debug msg="pulling blob "sha256:8dc8edf0ab44be350cd6b1018956aad594f7279daac0b78dc87e52b8b18560e0""
dockerd[1476]: time="2019-03-20T14:31:17.616397018+02:00" level=error msg="Download failed, retrying: received unexpected HTTP status: 503 Service Unavailable"

started yesterday. trying to get python:3.7 in a way to get homeassistant:latest

Not sure if this is the correct place to report this, so please point me in the right direction if this is not the right place.

I've got an official PHP container with a host

https://github.com/docker-library/repo-info/blob/master/repos/mariadb/remote/10-jammy.md#mariadb10-jammy

Platforms: 8

    linux; amd64
    unknown; unknown
    linux; arm64 variant v8
    unknown; unknown
    linux; ppc64le
    unknown; unknown
    linux; s390x
    unknown; unknown

Removed line in 3-jdk-8.md:

RUN apt-get update && apt-get install -y --no-install-recommends bzr git mercurial openssh-client subversion procps && rm -rf /var/lib/apt/lists/*