Docker: Issueshttps://projects.theforeman.org/https://projects.theforeman.org/favicon.ico?16970236342019-02-15T08:58:34ZForeman
Redmine Bug #26056 (New): API to list docker containers always retrun zero result https://projects.theforeman.org/issues/260562019-02-15T08:58:34ZMarek Hulánmhulan@redhat.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1677551">https://bugzilla.redhat.com/show_bug.cgi?id=1677551</a></p>
<p><strong>Description of problem:</strong> The API related to container list returns zero result</p>
<p>#hammer -d docker container list --compute-resource-id <compute-resource-id> shows zero result</p>
<p>or APi</p>
<p>curl -u admin:<password><a class="external" href="https://satellite.example.com/docker/api/v2/compute_resources/&lt;compute-resource-id&gt;/containers">https://satellite.example.com/docker/api/v2/compute_resources/&lt;compute-resource-id&gt;/containers</a></p>
<p>Returns zero result</p>
<p><strong>Version-Release number of selected component (if applicable):</strong> 6.5.0</p>
<p><strong>How reproducible:</strong> Always</p>
<p><strong>Actual results:</strong> Return zero result</p>
<p><strong>Expected results:</strong> Should return container list</p> Bug #21892 (New): Docker - containers log endpoint tries to connect to local /var/run/docker.sock...https://projects.theforeman.org/issues/218922017-12-06T12:51:23ZSebastian Gräßl
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1479291">https://bugzilla.redhat.com/show_bug.cgi?id=1479291</a></p>
<p><strong>Description of problem:</strong><br />Reading docker container logs does not work over tcp and keeps trying to connect to /var/run/docker.sock on the foreman host instead of using TCP/TLS for reaching the external docker interface.</p>
<p><strong>Steps to Reproduce:</strong><br />1. have an external host running docker, configured to accept tcp/tls connections<br />2. add a docker compute resource with tcp:// enabled<br />3. create a container via web interface<br />4. try to read the container logs via the web interface</p>
<p><strong>Actual results:</strong><br />2017-08-01 17:18:26 - nailgun.client - DEBUG - Making HTTP POST request to <a class="external" href="https://sat6.com/api/v2/compute_resources">https://sat6.com/api/v2/compute_resources</a> with options {'verify': False, 'auth': ('admin', 'changeme'), 'headers': {'content-type': 'application/json'}}, no params and data
{<br /> "compute_resource":
{<br /> "provider": "Docker",<br /> "url": "http://10.8.29.107:2375",<br /> "organization_ids": [55],<br /> "name": "ApReidcCPN" <br /> }<br />}.<br />2017-08-01 17:18:26 - nailgun.client - DEBUG - Received HTTP 201 response: {"description":null,"url":"http://10.8.29.107:2375","created_at":"2017-08-01 21:18:26 UTC","updated_at":"2017-08-01 21:18:26 UTC","id":52,"name":"ApReidcCPN","provider":"Docker","provider_friendly_name":"Docker","user":null,"images":[],"compute_attributes":[],"locations":[],"organizations":[{"id":55,"name":"zcBPUXbQHi","title":"zcBPUXbQHi","description":null}]}</p>
<p>2017-08-01 17:18:28 - nailgun.client - DEBUG - Making HTTP POST request to <a class="external" href="https://sat6.com/docker/api/v2/containers">https://sat6.com/docker/api/v2/containers</a> with options {'verify': False, 'auth': ('admin', 'changeme'), 'headers': {'content-type': 'application/json'}}, no params and data</p>
<p>{<br /> "container": {<br /> "repository_name": "busybox",<br /> "compute_resource_id": 52,<br /> "tag": "latest",<br /> "command": "date",<br /> "organization_ids": [55],<br /> "name": "hjRR6uiV1" <br /> }<br />}.<br />2017-08-01 17:18:36 - nailgun.client - DEBUG - Received HTTP 201 response<br />2017-08-01 17:18:36 - nailgun.client - DEBUG - Making HTTP GET request to <a class="external" href="https://sat6.com/docker/api/v2/containers/9/logs">https://sat6.com/docker/api/v2/containers/9/logs</a> with options {'verify': False, 'auth': ('admin', 'changeme'), 'headers': {'content-type': 'application/json'}}, no params and no data.<br />2017-08-01 17:18:36 - nailgun.client - WARNING - Received HTTP 500 response: {<br /> "error": {"message":"No such file or directory - connect(2) for /var/run/docker.sock (Errno::ENOENT)"}<br />}</p>
<p><strong>Expected results:</strong><br />connection is being made to the appropriate interface and the logs are being fetched</p> Feature #20775 (New): Exposed ports support for CLIhttps://projects.theforeman.org/issues/207752017-08-29T01:56:05ZSebastian Gräßl
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1335255">https://bugzilla.redhat.com/show_bug.cgi?id=1335255</a></p>
<p><strong>Description of problem:</strong><br />Similarly with UI Exposed ports support we need same support for CLI:<br />- hammer docker info<br />- hammer docker create<br />- hammer docker update</p>
<p><strong>Steps to Reproduce:</strong><br />1. hammer docker {info,create,update} sub commands lack support for docker exposed ports</p>
<p><strong>Actual results:</strong><br />missing support for exposed ports</p>
<p><strong>Expected results:</strong><br />exposed ports support implemented</p> Bug #20733 (New): Create Docker container issueshttps://projects.theforeman.org/issues/207332017-08-24T13:37:07ZAnonymous
<p>Hey,</p>
I'm using Foreman v1.15.3, Katello 3.4.4 and Docker plugin v3.2.1.<br />When i'm trying to create a container i get the errors in production.log:
<ul>
<li>Content View</li>
</ul>
<blockquote>
<p>API v1 - Repository images request failed</p>
</blockquote>
<p>After setting Content View, Repo etc. and clicking 'Next step' the input is resetted, so it's not possible to create a container with Content View.</p>
<ul>
<li>Docker hub or external registry (which is Docker hub in my setup - <a class="external" href="https://registry.hub.docker.com">https://registry.hub.docker.com</a>)</li>
</ul>
<blockquote>
<p>API v1 - Search failed</p>
</blockquote>
<p>Although the searching for container fails searching for tags does not.<br />If i ignore the failed search and go to the next step creation of the container succeed.</p> Feature #20093 (New): Display the power status for a Docker container via hammer https://projects.theforeman.org/issues/200932017-06-23T08:25:55ZDaniel Lobato Garciaelobatocs@gmail.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1247329">https://bugzilla.redhat.com/show_bug.cgi?id=1247329</a></p>
<p><strong>Description of problem:</strong></p>
<p>Currently hammer cli does not display the power status (running, stopped) for a given container, as shown below:</p>
<ol>
<li>hammer -u "${ADMIN_USER}" -p "${ADMIN_PASSWORD}" docker container info --id=1 --compute-resource="local_docker" <br />Name: docker-rhel-7-1<br />Image repository: rhel6.7<br />Tag: latest<br />Command: top<br />Compute resource: local_docker<br />Entrypoint:<br />CPU set:<br />CPU shares:<br />Memory (Bytes):<br />TTY: yes<br />Attach STDIN: no<br />Attach STDOUT: no<br />Attach STDERR: no<br />Registry: Red Hat Docker Registry<br />Created at: 2015/07/27 18:06:46<br />Updated at: 2015/07/27 18:06:46</li>
</ol>
<p>It would be great to be able to get this information, specially for automation tasks that may want to check this information before triggering some type of action based on the status.</p>
<p><strong>Version-Release number of selected component (if applicable):</strong></p>
<ul>
<li>Satellite 6.1.1 SNAP 14</li>
</ul>
<p><strong>How reproducible:</strong></p>
<p><strong>Steps to Reproduce:</strong><br />1. Provision a new docker container<br />2. Use hammer docker container info to find out what the power state is for the container<br />3.</p>
<p><strong>Actual results:</strong></p>
<p>This information is not currently displayed</p>
<p><strong>Expected results:</strong></p>
<p>Report the power status</p>
<p><strong>Additional info:</strong></p> Bug #14704 (New): Can't search external registry if username/password contains special charhttps://projects.theforeman.org/issues/147042016-04-19T04:50:52ZDaniel Lobato Garciaelobatocs@gmail.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1328082">https://bugzilla.redhat.com/show_bug.cgi?id=1328082</a> <br /> Description of problem:<br />Can't search a image/tag using an external registry if username/password contains special char. It seems that username/password is not URLEncoded when used.</p>
<p>Version-Release number of selected component (if applicable):<br />@Sat6.2.0-Beta-Snap8</p>
<p>How reproducible:<br />always</p>
<p>Steps to Reproduce:<br />1. Create an external registry using URL <a class="external" href="https://registry.access.redhat.com">https://registry.access.redhat.com</a> and username/password containing special char, e.g. '@', '%'<br />2. Go to New Container wizard and select an already created docker compute resouce<br />3. In the next step select the "External Registry" tab, search for 'rhel'</p>
<p>(x) Oops, we're sorry but something went wrong bad component(expected userinfo component or user component): q%r</p>
<p>Actual results:<br />No search results, an error message pop-up shown</p>
<p>Expected results:<br />Search results without errors.</p>
<p>Additional info:</p>
<p>2016-04-18 08:00:49 [app] [I] Started GET "/image_search/2/search_repository?search=rhel&registry_id=2" for <CLIENT_IP> at 2016-04-18 08:00:49 -0400<br />2016-04-18 08:00:49 [app] [I] Processing by ImageSearchController#search_repository as TEXT<br />2016-04-18 08:00:49 [app] [I] Parameters: {"search"=>"rhel", "registry_id"=>"2", "id"=>"2"}<br />2016-04-18 08:00:49 [app] [W] Action failed
| URI::InvalidComponentError: bad component(expected userinfo component or user component): q%r
| /opt/rh/rh-ruby22/root/usr/share/ruby/uri/generic.rb:400:in `check_user'
| /opt/rh/rh-ruby22/root/usr/share/ruby/uri/generic.rb:472:in `user='
| /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_docker-2.0.1.4/app/models/service/registry_api.rb:9:in `initialize'
| /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_docker-2.0.1.4/app/controllers/image_search_controller.rb:110:in `new'
| /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_docker-2.0.1.4/app/controllers/image_search_controller.rb:110:in `registry_search_image'
| /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_docker-2.0.1.4/app/controllers/image_search_controller.rb:42:in `block in search_repository'
| /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_docker-2.0.1.4/app/controllers/image_search_controller.rb:56:in `catch_network_errors'
| /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_docker-2.0.1.4/app/controllers/image_search_controller.rb:38:in `search_repository'
| /opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
| /opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/abstract_controller/base.rb:189:in `process_action'
| /opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/action_controller/metal/rendering.rb:10:in `process_action'<br /> ...<br />2016-04-18 08:00:49 [app] [I] Rendered common/500.html.erb (1.1ms)<br />2016-04-18 08:00:49 [app] [I] Completed 500 Internal Server Error in 12ms (Views: 1.5ms | ActiveRecord: 2.4ms)</p> Bug #14406 (New): Search works improperly for Docker(Hub) Container create procedurehttps://projects.theforeman.org/issues/144062016-03-31T02:34:58ZDaniel Lobato Garciaelobatocs@gmail.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1253589">https://bugzilla.redhat.com/show_bug.cgi?id=1253589</a> <br /> Description of problem:<br />Getting different error messages while trying to input any string in 'search' field of Docker Hub tab in new 'New Container'->'Image' section<br />That issue is referring to docker daemon 1.6.2 version</p>
<p>Version-Release number of selected component (if applicable):<br />RC1</p>
<p>How reproducible:<br />Always</p>
<p>Steps to Reproduce:<br />1. Create new Docker compute resource<br />2. Create Product and add Docker repository to it. (e.g. 'busybox' from 'https://registry.hub.docker.com')<br />3. Sync that repo (In result we should have repo with some Docker Images and some Docker Tags inside)<br />4. Push 'New Container' button<br />5. Preliminary->Deploy on->Select Docker compute resource from step 1<br />6. Next->Image->Docker Hub<br />7. Input any existing container name to search field(e.g. 'centos')</p>
<p>Actual results:<br />Getting error message in UI:<br />NoMethodError<br />undefined method `info' for nil:NilClass<br />app/models/concerns/foreman/thread_session.rb:33:in `clear_thread'<br />lib/middleware/catch_json_parse_errors.rb:9:in `call'</p>
<p>Expected results:<br />Container found and necessary tag displayed in the 'Tag' field</p>
<p>Additional info:</p>
<p>That behaviour was mentioned in 1253270 bug, but definitely worth to create separate defect</p> Bug #14405 (New): Display progress information when pulling Docker images onto a Compute Resourcehttps://projects.theforeman.org/issues/144052016-03-31T02:33:32ZDaniel Lobato Garciaelobatocs@gmail.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1206300">https://bugzilla.redhat.com/show_bug.cgi?id=1206300</a> <br /> Description of problem:</p>
<p>When creating a new container that requires a Docker image to be<br /> pulled down into the compute resource (e.g. choosing either the<br /> 'Docker Hub' or external 'Registry' and typing the name of an image<br /> that is not yet present in the compute resource), there's no visual<br /> information to the end user that something is happening and you're<br /> only redirected to the new container page once the image is pulled<br /> down. We need to handle this scenario the same way that we handle<br /> provisioning hosts and display progress like the orchestration<br /> progress bar displayed during host creation.</p>
<p>Please refer to <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1204925">https://bugzilla.redhat.com/show_bug.cgi?id=1204925</a></p>
<p>Version-Release number of selected component (if applicable):</p>
<ul>
<li>Satellite-6.1.0-RHEL-7-20150324.0</li>
</ul>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br />1. Create a Docker-based compute resource<br />2. Create a New Container and choose the Docker Hub tab after selecting your compute resource<br />3. Type 'wordpress' then click the search button (magnifying glass icon) to trigger a fetch to Docker Registry<br />4. Select a valid Tag and complete the wizard</p>
<p>Actual results:</p>
<p>Upon finishing the wizard, the user is not taken to the new container page until the 'wordpress' image is pulled down onto the computer resource.</p>
<p>Expected results:</p>
<ul>
<li>The user should be taken immediately to the new container page.</li>
<li>The 'Power On' button should be disabled until the docker image has been pulled and is ready.</li>
</ul>
<p>Additional info:</p> Bug #10197 (New): Changing tabs on New container wizard deselects external hub already selectedhttps://projects.theforeman.org/issues/101972015-04-17T16:23:44ZBryan Kearneybryan.kearney@gmail.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1190229">https://bugzilla.redhat.com/show_bug.cgi?id=1190229</a> <br /> Description of problem:<br />In the second step on the New Container wizard, if you select the "External registry" tab and a Registry, if you go to "Docker hub" tab and then go back on the "External registry" tab the previous state of Registry is lost.</p>
<p>Version-Release number of selected component (if applicable):<br />Satellite-6.1.0-RHEL-7-20150205.0</p>
<p>How reproducible:<br />Aways</p>
<p>Steps to Reproduce:<br />1. Containers > New Container<br />2. Select a Docker Compute resource and proceed to next step<br />3. Select External registry tab and select an already created registry.<br />4. Go to the Docker hub tab<br />5. Go back to the External registry tab</p>
<p>Actual results:<br />The previous selected Registry is cleaned</p>
<p>Expected results:<br />The previous selected registry remains when changing tabs</p>
<p>Additional info:</p>