3.6. Container Management Issues

This section describes known issues with the Container Management component of Satellite 6.1.
BZ 1223547: When a command cannot be found in a Docker container the error displayed complains about HTTP error code
Issue

If you pass an invalid command to a container, the system returns an HTTP 404 Not Found error, instead of informing the user that the command itself was invalid or not found. For example, the web UI displays the following error: 

"Error - Expected([200, 201, 202, 203, 204, 304]) <=> Actual(404 Not Found)"
Workaround

None at this time.

BZ 1230930: Cannot create external registries using the API or CLI
Satellite 6 has the ability to inspect not only the official docker registry (registry.hub.docker.com) but also to inspect custom registries. This is described in the section "Working with Containers" in the Red Hat Satellite User Guide.
Issue

The ability to add a custom registry is currently only available through the web UI, not using hammer (CLI) or the API. You need to use the web UI to create an external registry and then reference that registry and not the official one. This registry is used to create containers using the External Registry tab in order to search for the desired image and select a tag. Satellite then pulls the image from the custom registry and creates the container.

BZ 1246265: Cannot provision Docker container straight from an external Red Hat registry
Issue

If you use the New Container wizard to try to provision a new Docker container directly from the Red Hat registry, the provisioning process fails with no indication in the UI as to what has happened.

This issue appears in the following scenario:
  1. Create a new container Registry pointing at http://registry.access.redhat.com
  2. Create a new Docker compute resource
  3. Create a new Docker container, choosing the Registry option from the Wizard and selecting the Red Hat registry
A message similar to the following might appear in /var/log/messages: 
Jul 23 16:11:52 ibm-06 docker: v1 ping attempt failed with error: Get https://registry.access.redhat.com:/v1/_ping: dial tcp 10.44.256.99:0: connection refused. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry registry.access.redhat.com:` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/registry.access.redhat.com:/ca.crt
Workaround

You can work around this issue by using HTTPS instead of HTTP.