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

pullImageFromManifest does not use Skopeo auth #137

Open
remi-gelinas opened this issue Jun 19, 2024 · 0 comments
Open

pullImageFromManifest does not use Skopeo auth #137

remi-gelinas opened this issue Jun 19, 2024 · 0 comments

Comments

@remi-gelinas
Copy link

remi-gelinas commented Jun 19, 2024

I'm trying to use nix2container to set up builds based on a base image from a private ECR repository. pullImage works fine as it uses the passthrough /etc/skopeo/auth.json sandbox path, but pullImageFromManifest doesn't seem to leverage skopeo anywhere in the build, and therefore can't authenticate to our repo. Considering the manifest doesn't have any auth tokens in it, I'm unclear as to how one is supposed to provide authentication for a registry using pullImageFromManifest.

Inconsistently, the generated getManifest script to update manifests from an image generated by pullImageFromManifest DOES use Skopeo, and has no problem authenticating to the registry.

The docs make it seem like the auth sandbox passthrough should work for both versions of image pulling, but as far as I can tell, only pullImage picks up the correct auth.

Is this intentional? Is there another undocumented method to provide auth info to pullImageFromManifest?

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

No branches or pull requests

1 participant