Panamax unable to start images from private registry

[mikesplain]

I setup a coreos box in openstack and got Panamax up and running. Things look great! I also have a simple registry server running on a different VM. The easy way I've found to setup a fast registry server and get it working is to tag images as <registry server fqdn>:5000/<imagename>.

I noticed a number of things in Panamax:

• I thought I would be able to have Panamax query the registry by just copy and pasting this name in the image search (my assumption may be wrong).
• If I ssh to the coreos box and do a docker pull on the images to get local, then try to get that image running in Panamax, Panamax recognizes the name of the image as the fqdn of the server, then tag as :5000/<imagename>. I would expect it to find the image name as either <imagename> or <fqdn>:5000.

Please let me know if I'm missing something here. If this is a new issue, I'll probably need help debugging and where to determine if issues should be opened under the API or other pieces of Panamax.

Thanks!

[rupakg]

@mikesplain Panamax currently only supports searching the Docker Hub. We have a feature request to enable private registries on our feedback channel. Please vote for it there.

On your second point, we will investigate to see why the name of the image is getting fudged.

Thanks for bringing up the issue.

[bdehamer]

Searching a private registry is a new feature request, but the issue of not being able to use a local image that was pulled from a private registry is definitely a bug.

[mikesplain]

Awesome thanks!

[alexwelch]

you got it.