8000 [19.03] Keep but deprecate registry v2 schema1 logic and revert to libtrust-key-based engine ID by tiborvass · Pull Request #284 · docker-archive/engine · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Oct 13, 2023. It is now read-only.

Conversation

tiborvass
Copy link
@tiborvass tiborvass commented Jun 14, 2019

Cherry-pick of moby#39365

@tiborvass tiborvass requested a review from justincormack June 14, 2019 21:11
Copy link
Member
@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM if green

@thaJeztah thaJeztah added this to the 19.03.0 milestone Jun 14, 2019
Tibor Vass added 7 commits June 18, 2019 18:54
This reverts commit 13b7d11.

Signed-off-by: Tibor Vass <tibor@docker.com>
(cherry picked from commit f23a51a)
Signed-off-by: Tibor Vass <tibor@docker.com>
Signed-off-by: Tibor Vass <tibor@docker.com>
(cherry picked from commit 0811297)
Signed-off-by: Tibor Vass <tibor@docker.com>
This reverts commit 98fc091 in order to
keep registry v2 schema1 handling and libtrust-key-based engine ID.

Because registry v2 schema1 was not officially deprecated and
registries are still relying on it, this patch puts its logic back.

However, registry v1 relics are not added back since v1 logic has been
removed a while ago.

This also fixes an engine upgrade issue in a swarm cluster. It was relying
on the Engine ID to be the same upon upgrade, but the mentioned commit
modified the logic to use UUID and from a different file.

Since the libtrust key is always needed to support v2 schema1 pushes,
that the old engine ID is based on the libtrust key, and that the engine ID
needs to be conserved across upgrades, adding a UUID-based engine ID logic
seems to add more complexity than it solves the problems.

Hence reverting the engine ID changes as well.

Signed-off-by: Tibor Vass <tibor@docker.com>
(cherry picked from commit f695e98)
Signed-off-by: Tibor Vass <tibor@docker.com>
Signed-off-by: Tibor Vass <tibor@docker.com>
(cherry picked from commit 53dad9f)
Signed-off-by: Tibor Vass <tibor@docker.com>
Signed-off-by: Tibor Vass <tibor@docker.com>
(cherry picked from commit f923321)
Signed-off-by: Tibor Vass <tibor@docker.com>
This will add a warning log in the daemon, and will send the message
to be displayed by the CLI.

Signed-off-by: Tibor Vass <tibor@docker.com>
(cherry picked from commit d35f8f4)
Signed-off-by: Tibor Vass <tibor@docker.com>
…revert

Signed-off-by: Tibor Vass <tibor@docker.com>
(cherry picked from commit 3f1cdd5)
Signed-off-by: Tibor Vass <tibor@docker.com>
@tiborvass tiborvass force-pushed the 19.03-revert-remove-legacy-registry branch from 0a272ba to e61e107 Compare June 18, 2019 18:55
@tiborvass tiborvass changed the title [19.03] Revert "Remove the rest of v1 manifest support" [19.03] Keep but deprecate registry v2 schema1 logic and revert to libtrust-key-based engine ID Jun 18, 2019
@tiborvass
Copy link
Author

@andrewhsu @thaJeztah updated with clean cherry-picks

Copy link
@andrewhsu andrewhsu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@andrewhsu andrewhsu merged commit b07f53d into docker-archive:19.03 Jun 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

0