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.

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

Bump stargz-snapshotter and partial registry logic integration #1760

Merged
merged 1 commit into from
Oct 29, 2020

Conversation

ktock
Copy link
Collaborator

@ktock ktock commented Oct 29, 2020

Following-up: #1666 (comment)

#1733 is WIP but this PR is mainly focusing on bumping up the snapshotter pkg and applying bug fixes.
Full diff: containerd/stargz-snapshotter@2ee75e9...3a04e4c
This removes the dependency on github.com/google/go-containerregistry.

Current stargz snapshotter pkg doesn't contain registry configuration and the client of that pkg needs to pass it to that pkg. So this commit includes changes of propagating buildkitd's registry configuration (docker.RegistryHosts) to stargz snapshotter.

But this is a partial integration of registry logic between buildkitd and stargz snapshotter because buildkitd's session-based authentication logic ((util/resolver).dockerAuthorizer) is still not applied to stargz snapshotter. This means private images that require ~/.docker/config.json creds can't be lazily pulled yet. Further discussion towards the session-based authentication integration is in progress at #1733 .

Current stargz snapshotter pkg doesn't contain registry configuration and the
client of that pkg needs to pass it to that pkg. So this commit includes changes
of propagating buildkitd's registry configuration to stargz snapshotter.

But this is a partial integration of registry logic between buildkitd and stargz
snapshotter because buildkitd's session-based authentication logic is still not
applied to stargz snapshotter. This means private images that require
`~/.docker/config.json` creds can't be lazily pulled yet.

Signed-off-by: ktock <ktokunaga.mail@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants