Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1147357 [details]
production.log

Description of problem:
unable to create docker container in external docker compute resource

Version-Release number of selected component (if applicable):
satellite-6.2.0-8.0.beta.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create an external docker compute resource
2. Create a docker product with one or more docker repo, publish/promote
3. Create a new container using the compute resource from step 1 and using the docker repos from step 2

Actual results:
Oops, we're sorry but something went wrong undefined method `full_messages' for []:Array

Expected results:
Docker container is created

Additional info:

Possibly NOTABUG...

Do you have bootstrap certs installed on a remote docker host?

@Lukas, thanks yeah this is what I  meant in Comment 2. I will get to this today.

I created a new docker host and tried this again and it worked.

Fwiw, I used my docker Compute resource as http://$dockerhost:2375 and installed my katello cert in the docker host.  I was able to create a new container.