[portus] Unable to push to registry v. 2.0.5

[ntwrkguru]

Unable to push to the registry on a fresh install of Portus (v. 2.0.5). Looks like it's attempting to push using the v1 API.

App 152 stderr: Started PUT "/v1/repositories/ssteiner/busybox/" for 172.29.98.178 at 2017-03-15 13:09:42 +0000

On the client side, here is the reproduction (sanitized as needed):

% docker tag busybox:latest registry.example.com:443/ssteiner/busybox:latest
% docker push registry.example.com:443/ssteiner/busybox:latest
The push refers to a repository [registry.example.com:443/ssteiner/busybox]
c0de73ac9968: Preparing 
Error: Status 404 trying to push repository ssteiner/busybox: ""

Client information:
Docker for Mac-

r$ docker version
Client:
 Version:      17.03.0-ce
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   60ccb22
 Built:        Thu Feb 23 10:40:59 2017
 OS/Arch:      darwin/amd64

Server:
 Version:      17.03.0-ce
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   3a232c8
 Built:        Tue Feb 28 07:52:04 2017
 OS/Arch:      linux/amd64
 Experimental: true

docker-machine-

% docker version
Client:
 Version:      17.03.0-ce
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   60ccb22
 Built:        Thu Feb 23 10:40:59 2017
 OS/Arch:      darwin/amd64

Server:
 Version:      17.03.0-ce
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   3a232c8
 Built:        Tue Feb 28 07:52:04 2017
 OS/Arch:      linux/amd64
 Experimental: false

Server-side:

$ docker version
Client:
 Version:      17.03.0-ce
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   60ccb22
 Built:        Thu Feb 23 10:57:47 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.0-ce
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   60ccb22
 Built:        Thu Feb 23 10:57:47 2017
 OS/Arch:      linux/amd64
 Experimental: false

• I've tried specifying :443 or omitting :443 with the same results
• I've tried using both Docker for Mac and docker-machine with the same results

Any ideas?

[flavio]

@mssola any idea about this one?

[ntwrkguru]

Downgraded the server host to docker engine 1.13.1 and even to 1.8.3 and see the same.

[mssola]

@ntwrkguru what about Docker distribution, what's the version there ?

[ntwrkguru]

@mssola how do I determine that?

[ntwrkguru]

I assumed a registry was included. Guess not. I spun one up on the same box:

$ docker exec -it registry registry -v
registry github.com/docker/distribution v2.6.0

and linked to it from portus:

$ docker exec -it portus cat /etc/hosts
127.0.0.1	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
192.168.66.4	registry c7af1d32eb9f
192.168.66.2	portus-db 2b1627530079
192.168.66.3	40502cd04277

Then changed the registry in Portus UI to be registry:5000 (non-ssl). I still see the same thing. Looks like there is no tests performed when adding a registry; it just assumes it will be there and responding according to the configuration?

[ntwrkguru]

@mssola Can you offer any guidance on this? I have the registry now installed and can login to it, but still seeing that error when attempting to push.