As part of Katello 2.5, we are working to add support the Docker v2
registry API[1]. Unfortunately, the v2 registry API uses different data
structures than v1 to manage images. There is no straightforward
migration path to get data out of v1 and into v2 via either
pulp-manage-db or via Katello rake tasks.
Our current plan is to remove support for Docker registry v1 in Katello
2.5 and introduce v2 support. This means that Docker repos currently
managed in Katello 2.4 will disappear and will need to re-created and
re-synced from an upstream source. We can provide warnings and
instructions on this as part of the 2.5 release notes, but users will be
on their own for ensuring that that custom content is not lost.
If you have questions or concerns about this, let us know and we'll try
to address them. Thanks!
What happens to content views that contain Docker content?
···
On Thu, Jan 28, 2016 at 12:30 PM, Chris Duryee wrote:
As part of Katello 2.5, we are working to add support the Docker v2
registry API[1]. Unfortunately, the v2 registry API uses different data
structures than v1 to manage images. There is no straightforward
migration path to get data out of v1 and into v2 via either
pulp-manage-db or via Katello rake tasks.
Our current plan is to remove support for Docker registry v1 in Katello
2.5 and introduce v2 support. This means that Docker repos currently
managed in Katello 2.4 will disappear and will need to re-created and
re-synced from an upstream source. We can provide warnings and
instructions on this as part of the 2.5 release notes, but users will be
on their own for ensuring that that custom content is not lost.
If you have questions or concerns about this, let us know and we’ll try
to address them. Thanks!
> What happens to content views that contain Docker content?
Apologies for the late reply.
Docker v1 repos in CVs will also be deleted.
···
On 01/28/2016 12:39 PM, Eric D Helms wrote:
On Thu, Jan 28, 2016 at 12:30 PM, Chris Duryee cduryee@redhat.com wrote:
As part of Katello 2.5, we are working to add support the Docker v2
registry API[1]. Unfortunately, the v2 registry API uses different data
structures than v1 to manage images. There is no straightforward
migration path to get data out of v1 and into v2 via either
pulp-manage-db or via Katello rake tasks.
Our current plan is to remove support for Docker registry v1 in Katello
2.5 and introduce v2 support. This means that Docker repos currently
managed in Katello 2.4 will disappear and will need to re-created and
re-synced from an upstream source. We can provide warnings and
instructions on this as part of the 2.5 release notes, but users will be
on their own for ensuring that that custom content is not lost.
If you have questions or concerns about this, let us know and we’ll try
to address them. Thanks!
