Project

General

Profile

Bug #9756

Unable to provision container via private registry / no username, password

Added by Jay Christopherson almost 8 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

I just installed version 1.2.2 of the docker plugin. Foreman version is 1.7.1, running on CentOS.

I registered a private registry that requires no authentication (no username, password). When I try to launch a container, I'm able to find my images, but on "Submit", nothing happens. I can find no log output either, other than a POST event in the server logs.

I am able to successfully launch containers from the public registry, as well as register compute resources, see running containers, stop/start/delete containers, etc... so I believe the plugin is installed correctly. It's just this particular use case that does not appear to work.

I'm happy to provide any logs or output that I can, but as I mentioned, I can find nothing in the standard log files.

History

#1 Updated by Jay Christopherson almost 8 years ago

Jay Christopherson wrote:

I just installed version 1.2.2 of the docker plugin. Foreman version is 1.7.1, running on CentOS.

I registered a private registry that requires no authentication (no username, password). When I try to launch a container, I'm able to find my images, but on "Submit", nothing happens. I can find no log output either, other than a POST event in the server logs.

I am able to successfully launch containers from the public registry, as well as register compute resources, see running containers, stop/start/delete containers, etc... so I believe the plugin is installed correctly. It's just this particular use case that does not appear to work.

I'm happy to provide any logs or output that I can, but as I mentioned, I can find nothing in the standard log files.

FWIW, I enabled debug in production.rb, following the FAQ on troubleshooting, but I do not see any new output in the logs.

Also available in: Atom PDF