https://bugzilla.redhat.com/show_bug.cgi?id=1218639
--- Comment #7 from Luwen Su <lsu(a)redhat.com> ---
In docker-1.6.2-10.el7.x86_64
start daemon as #docker -d -D &
#docker push docker.io/timesu/busybox
INFO[0199] -job push(docker.io/timesu/busybox) = ERR (1)
Please login prior to push:
Username: timesu
Password:
Email: timesuss(a)hotmail.com
EBU[0221] Calling POST /auth
INFO[0221] POST /v1.18/auth
INFO[0221] +job auth()
INFO[0221] +job resolve_index(https://index.docker.io/v1/)
INFO[0222] -job resolve_index(https://index.docker.io/v1/) = OK (0)
DEBU[0222] pinging registry endpoint
https://index.docker.io/v1/
DEBU[0222] attempting v1 ping for registry endpoint
https://index.docker.io/v1/
DEBU[0222] attempting v1 login to registry endpoint
https://index.docker.io/v1/
DEBU[0223]
https://index.docker.io/v1/users/ -- HEADERS:
map[User-Agent:[docker/1.6.2 go/go1.4.2 kernel/3.10.0-243.el7.x86_64 os/linux
arch/amd64]]
But once i pushed
# docker push time/busybox
DEBU[0425] pinging registry endpoint
https://index.docker.io/v1/
DEBU[0425] attempting v1 ping for registry endpoint
https://index.docker.io/v1/
Repository does not exist: docker.io/time/busybox
INFO[0425] -job push(time/busybox) = ERR (1)
The push refers to a repository [docker.io/time/busybox] (len: 0)
FATA[0001] Repository does not exist: docker.io/time/busybox
#docker tag time/busybox docker.io/time/busybox will workaround it, means
#docker push time/busybox success after there is a docker.io/time/busybox
--
You are receiving this mail because:
You are on the CC list for the bug.