Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use a blank docker config file to avoid issues with the requiring credentials for public gcr.io images #1125

Closed
wants to merge 2 commits into from
Closed

Use a blank docker config file to avoid issues with the requiring credentials for public gcr.io images #1125

wants to merge 2 commits into from

Commits on Mar 12, 2020

  1. Ensure we use a blank docker config file to avoid issues with the def… 

    …ault config.json which requires credentials accessing gcr.io registries

- Users who require credentials will need to supply their own config.json file anyway,
  so let them set it up as needed.
    @filesnate
    filesnate committed Mar 12, 2020
    Configuration menu
    Copy the full SHA
    24268d6 View commit details
    Browse the repository at this point in the history

Commits on Mar 14, 2020

  1. Remove importing gcr images into docker registry 

    Previously there was a need to import public GCR images into the local
docker registry and replace the base images to use the local docker
registry. This is no longer needed since Kaniko now works with public
GCR images also for unauthenticated users.
    @samos123
    samos123 committed Mar 14, 2020
    Configuration menu
    Copy the full SHA
    aa9ffc1 View commit details
    Browse the repository at this point in the history