Bug #8409: Failure when creating a container with an image not in the host - Docker - Foreman

Bug #8409

Failure when creating a container with an image not in the host

Added by Daniel Lobato Garcia over 8 years ago. Updated almost 8 years ago.

Status:

Closed

Priority:

High

Assignee:

Category:

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman-docker/pull/65

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

If the compute resource docker host does not have the image, creation will fail, fog will return a 404.
The images should be pulled from the registry on creation asynchronously, and display progress like the orchestration progress bar displayed during host creation.

Related issues

Associated revisions

Revision b747db40 (diff)
Added by Partha Aji about 8 years ago

Refs #8409 - Partially addressing pull before create container

Inital code to do a pull of an image before creating a container.
Note likely this part is going to change once we add foreman tasks but
this is the start point.

Revision b747db40 (diff)
Added by Partha Aji about 8 years ago

Refs #8409 - Partially addressing pull before create container

Inital code to do a pull of an image before creating a container.
Note likely this part is going to change once we add foreman tasks but
this is the start point.

Revision 16234b27 (diff)
Added by Daniel Lobato Garcia about 8 years ago

Fixes #8409 - Pull docker image asynchronously

Revision 16234b27 (diff)
Added by Daniel Lobato Garcia about 8 years ago

Fixes #8409 - Pull docker image asynchronously

History

#1 Updated by Partha Aji over 8 years ago

Blocks Tracker #7125: Docker Content Support added

#2 Updated by Partha Aji over 8 years ago

Basically foreman-docker does not do a docker pull before trying to create a container with the pulled image. We need to add something that looks like
""
::Docker::Image.create({:fromImage => "registry:5000/<repo>", :tag => "latest"} )
""
before creating container