Story #798
closed
Track image ancestry
0%
Description
When a docker image with multiple layers is uploaded to Pulp, each layer is a distinct unit. We need a way to query which layers are related to given image ID. Here's a couple example workflows:
- Moving or Copying an image between repositories; ancestors would have to come along for the ride if they are not in the destination repository
- Removing an image from a repository; the ancestors unique to that also be removed (see #159)
Updated by mhrivnak about 9 years ago
Copy already brings all dependent layers that are in the current repo, so that's a solved problem.
Pulp currently adds a parent ID to every docker image, so it's easy to construct the ancestry tree within any repo. If you need to operate on part of a tree in the short-term (such as removing a branch only up to a fork), I suggest doing this client-side. We will brainstorm on how to facilitate purging of untagged branches in the tree, but it will be difficult to do without a custom API just for docker.
Updated by jgreguske about 9 years ago
mhrivnak wrote:
Copy already brings all dependent layers that are in the current repo, so that's a solved problem.
Pulp currently adds a parent ID to every docker image, so it's easy to construct the ancestry tree within any repo. If you need to operate on part of a tree in the short-term (such as removing a branch only up to a fork), I suggest doing this client-side. We will brainstorm on how to facilitate purging of untagged branches in the tree, but it will be difficult to do without a custom API just for docker.
Ok, when should I expect a response after the brainstorming? If 2.5 handles this already we can continue the conversations in #159 if you prefer.
Updated by bmbouter about 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter about 5 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Added by Mike DePaulo over 2 years ago
Added by Mike DePaulo over 2 years ago
Revision b4dd10d0 | View on GitHub
When installing from packages, fix pulpcore getting upgraded prematurely
during "pulp_common : Install the Pulp undeclared yum package dependencies" by no longer installing pulpcore-selinux there. pulpcore-selinux will be installed as a declared dependency of pulpcore.
fixes: #798
.
When installing from packages, fix pulpcore getting upgraded prematurely
during "pulp_common : Install the Pulp undeclared yum package dependencies" by no longer installing pulpcore-selinux there. pulpcore-selinux will be installed as a declared dependency of pulpcore.
fixes: #798