Actions
Bug #8409
closed
Failure when creating a container with an image not in the host
Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
-
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.
Updated by Partha Aji over 9 years ago
- Blocks Tracker #7125: Docker Content Support added
Updated by Partha Aji over 9 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
Updated by Daniel Lobato Garcia over 9 years ago
- Priority changed from Normal to High
Updated by The Foreman Bot over 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-docker/pull/65 added
- Pull request deleted (
)
Updated by Daniel Lobato Garcia about 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman-docker|16234b270677486ea197a0dca54b14ed981abfc5.
Updated by Dominic Cleal about 9 years ago
- Status changed from Closed to Ready For Testing
Reverted in https://github.com/theforeman/foreman-docker/commit/e054355497e8e0dd4cbad25e0e735638fb9afef7 due to accidental merge.
Updated by David Davis about 9 years ago
- Status changed from Ready For Testing to Closed
Actions