Feature #13481
closed
Ensure foreman_docker works as expected with docker v2 changes
Added by Chris Duryee almost 9 years ago.
Updated over 6 years ago.
Description
This task has two parts:
- confirm that foreman_docker works, specifically the "content view" tab that displays when it is installed with Katello.
- if any changes are needed to work with manifests instead of images, create PR for said changes
Ran some basic tests and it appears to be functioning well without any changes.
Tested:
1. deploying a container using a lifecycle environment / content view. The view contained the centos manifest and the container was executed to perform a '/bin/ping -c 50 www.google.com'
2. deploying a container using an image from dockerhub (centos, 7.0.1406). The container was exectued to perform a '/bin/ping -d 50 www.google.com'
Both scenarios executed successfully.
In scenario 1, observed it pull the content from katello (e.g. Trying to pull katello-2-8-dev:5000/default_organization-dev-docker_centos_view_1-docker-brad1-centos from https://katello-2-8-dev:5000 v2)
In scenario 2, observed it pull the content from dockerhub (e.g. Trying to pull docker.io/centos from https://registry-1.docker.io v2)
- Status changed from New to Closed
marking as closed based on Brad's findings.
- Status changed from Closed to Resolved
- Translation missing: en.field_release set to 86
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by