Skip to content

Conversation

@thaJeztah
Copy link
Member

Deprecation of interacting with v1 registries was started in docker 1.8.3, which added a --disable-legacy-registry flag.

This option was announced to be the default starting with docker 17.06, and v1 registries completely removed in docker 17.12.

This patch updates the default, and disables interaction with v1 registres by default.

ping @dmcgowan @aaronlehmann

@thaJeztah
Copy link
Member Author

Found some tests that need updating;

  • DockerRegistryAuthHtpasswdSuite.TestLogoutWithExternalAuth looks to depend on v1 registry fallback as well
  • DockerRegistryAuthHtpasswdSuite.TestPullNoCredentialsNotFound needs to be updated, because it uses fallback to v1 registries

@thaJeztah thaJeztah force-pushed the disable-v1-registry-by-default branch from 7b596ae to 6dc304b Compare June 12, 2017 09:02
Deprecation of interacting with v1 registries was
started in docker 1.8.3, which added a `--disable-legacy-registry`
flag.

This option was anounced to be the default starting
with docker 17.06, and v1 registries completely
removed in docker 17.12.

This patch updates the default, and disables
interaction with v1 registres by default.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
@thaJeztah thaJeztah force-pushed the disable-v1-registry-by-default branch from 6dc304b to 2b8f0ee Compare June 12, 2017 09:04
@thaJeztah
Copy link
Member Author

Tests were updated; all green now

Copy link
Contributor

@mlaventure mlaventure left a comment

Choose a reason for hiding this comment

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

LGTM

@aaronlehmann
Copy link

LGTM

Not sure about doing this after the freeze, but not I'm not going to block this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants