Bug 211041 - sysutils/docker-freebsd: Repository not found when pulling image
Summary: sysutils/docker-freebsd: Repository not found when pulling image
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: Jochen Neumeister
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2016-07-12 18:55 UTC by Rares Vernica
Modified: 2020-01-11 11:12 UTC (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rares Vernica 2016-07-12 18:55:27 UTC 
Docker pull gets interrupted when pulling the centos image. Other images pull ok.

> docker pull centos
latest: Pulling from centos

3690474eb5b4: Pull complete 
01bdb2286ef2: Extracting [========>                                          ] 12.26 MB/70.6 MB
6930af01dfa2: Download complete 
3aa28fd030d9: Download complete 
Pulling repository centos
Repository not found


Version info:

> uname -a
FreeBSD ... 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25 02:10:02 UTC 2016     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
> pkg info docker-freebsd
docker-freebsd-20150625
Name           : docker-freebsd
Version        : 20150625
Installed on   : Mon Jul 11 05:40:46 2016 PDT
Origin         : sysutils/docker-freebsd
Architecture   : freebsd:10:x86:64
Comment 1 Rares Vernica 2016-07-12 18:58:24 UTC 
I tried pulling the image multiple times, just to make sure it is not a transient network error, but it always fails at the exact same point.
Comment 2 Yonas Yanfa 2016-10-26 13:51:27 UTC 
I'm seeing this error for the centos image as well. It doesn't happen when pulling the ubuntu image, though.
Comment 3 ganthore 2017-05-30 02:34:41 UTC 
Works fine for CentOS 6 but always fails on latest (7)...

CentOS 6:

# docker pull centos:6
6: Pulling from centos

afd1fcad9387: Pull complete
0d09530010f4: Pull complete
87fe14395856: Pull complete
Digest: sha256:c2306cca701a8713c4ad2d61971d5d1034304ffc1b933ffe57984be61f4e93c7
Status: Downloaded newer image for centos:6

CentOS 7:

# docker pull centos:7
7: Pulling from centos

5932f74ff0cd: Extracting [========>                                          ]  11.7 MB/70.52 MB
4a7b890637c2: Download complete
4beff0251382: Download complete
Pulling repository centos
Repository not found
Comment 4 beatgammit 2017-07-27 18:03:34 UTC 
Does anyone have any idea how to debug this? I'm willing to do some investigation work, but I don't really know the best place to start. Looking through the documentation, it looks like docker has moved the code to the moby project[1].

From the wiki[2], there is a link to the project on Github[3] for porting docker to FreeBSD, yet the latest commit on that branch is from 2015.

Is this still building with the code from 2015, or have the changes been merged upstream to moby? According to the moby project, as of February of this year it hadn't been upstreamed[4].

I'd like to help where I can, but I don't know where to start.

- [1] - https://github.com/moby/moby
- [2] - https://wiki.freebsd.org/Docker
- [3] - https://github.com/kvasdopil/docker/tree/freebsd-compat
- [4] - https://github.com/moby/moby/issues/31303
Comment 5 ksmakoto 2017-08-10 03:14:52 UTC 
Hi, I surveyed this problem. See my memo.
http://metanest.jp/freebsd_docker_centos7.html
Comment 6 Tobias Kortkamp freebsd_committer freebsd_triage 2018-11-14 10:41:41 UTC 
Reset assignee.  kmoore@ has dropped maintainership in ports r434114.
The port currently has no maintainer.
Comment 7 Kubilay Kocak freebsd_committer freebsd_triage 2019-01-07 10:50:36 UTC 
Assign to new recent maintainer, see: ports r489312
Comment 8 Walter Schwarzenfeld freebsd_triage 2019-08-05 22:50:47 UTC 
EXPIRATION_DATE=        2019-09-04.
Comment 9 Rene Ladan freebsd_committer freebsd_triage 2020-01-11 11:12:25 UTC 
So there seems a workaround but this port expired yesterday due to build errors.