Skip to content

[build]: Allow build-time specification of alternative docker registries#8134

Merged
lguohan merged 1 commit intosonic-net:masterfrom
jusherma:jusherma/registry-variables
Jul 14, 2021
Merged

[build]: Allow build-time specification of alternative docker registries#8134
lguohan merged 1 commit intosonic-net:masterfrom
jusherma:jusherma/registry-variables

Conversation

@jusherma
Copy link
Copy Markdown
Contributor

@jusherma jusherma commented Jul 9, 2021

Why I did it

Allows users to host their own local docker registries and utilize them via the REGISTRY_SERVER and REGISTRY_PORT environmental variables

How I did it

Only set REGISTRY_SERVER and REGISTRY_PORT in rules/config if they are unset.

How to verify it

  1. Export environmental variables REGISTRY_SERVER and REGISTRY_PORT to an alternative docker registry. Export the environmental variable ENABLE_DOCKER_BASE_PULL to y.
  2. Ensure the required sonic-slave docker images are not present locally, but are available in the docker registry
  3. Execute make init and make configure
  4. Confirm that the appropriate docker images were pulled from the appropriate docker registry, and not built locally

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106

Description for the changelog

Allow build-time specification of alternative docker registries

A picture of a cute animal (not mandatory but encouraged)

image

@lguohan lguohan changed the title Allow build-time specification of alternative docker registries [build]: Allow build-time specification of alternative docker registries Jul 14, 2021
@lguohan lguohan merged commit ad3f861 into sonic-net:master Jul 14, 2021
qiluo-msft pushed a commit that referenced this pull request Jul 15, 2021
…ies (#8134)

Why I did it
Allows users to host their own local docker registries and utilize them via the REGISTRY_SERVER and REGISTRY_PORT environmental variables

How I did it
Only set REGISTRY_SERVER and REGISTRY_PORT in rules/config if they are unset.

How to verify it
Export environmental variables REGISTRY_SERVER and REGISTRY_PORT to an alternative docker registry. Export the environmental variable ENABLE_DOCKER_BASE_PULL to y.
Ensure the required sonic-slave docker images are not present locally, but are available in the docker registry
Execute make init and make configure
Confirm that the appropriate docker images were pulled from the appropriate docker registry, and not built locally
judyjoseph pushed a commit that referenced this pull request Aug 4, 2021
…ies (#8134)

Why I did it
Allows users to host their own local docker registries and utilize them via the REGISTRY_SERVER and REGISTRY_PORT environmental variables

How I did it
Only set REGISTRY_SERVER and REGISTRY_PORT in rules/config if they are unset.

How to verify it
Export environmental variables REGISTRY_SERVER and REGISTRY_PORT to an alternative docker registry. Export the environmental variable ENABLE_DOCKER_BASE_PULL to y.
Ensure the required sonic-slave docker images are not present locally, but are available in the docker registry
Execute make init and make configure
Confirm that the appropriate docker images were pulled from the appropriate docker registry, and not built locally
carl-nokia pushed a commit to carl-nokia/sonic-buildimage that referenced this pull request Aug 7, 2021
…ies (sonic-net#8134)

Why I did it
Allows users to host their own local docker registries and utilize them via the REGISTRY_SERVER and REGISTRY_PORT environmental variables

How I did it
Only set REGISTRY_SERVER and REGISTRY_PORT in rules/config if they are unset.

How to verify it
Export environmental variables REGISTRY_SERVER and REGISTRY_PORT to an alternative docker registry. Export the environmental variable ENABLE_DOCKER_BASE_PULL to y.
Ensure the required sonic-slave docker images are not present locally, but are available in the docker registry
Execute make init and make configure
Confirm that the appropriate docker images were pulled from the appropriate docker registry, and not built locally
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