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

apt google cloud repository changed Origin/Label: consider updating base image #1310

Closed
francesco-ballarin opened this issue Oct 19, 2023 · 1 comment

Comments

@francesco-ballarin
Copy link

Running apt update inside a current kaggle docker image gives

Get:1 https://packages.cloud.google.com/apt cloud-sdk InRelease [6361 B]
Get:2 http:https://packages.cloud.google.com/apt gcsfuse-focal InRelease [1299 B]    
Get:3 https://packages.cloud.google.com/apt cloud-sdk/main amd64 Packages [530 kB]m
Hit:4 http:https://archive.ubuntu.com/ubuntu focal InRelease                    
Get:5 http:https://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
E: Repository 'http:https://packages.cloud.google.com/apt gcsfuse-focal InRelease' changed its 'Origin' value from 'gcsfuse-jessie' to 'namespaces/gcs-fuse-prod/repositories/gcsfuse-focal'
E: Repository 'http:https://packages.cloud.google.com/apt gcsfuse-focal InRelease' changed its 'Label' value from 'gcsfuse-jessie' to 'namespaces/gcs-fuse-prod/repositories/gcsfuse-focal'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Can you considering updating the base image from tag m111 to a later one? For instance, m112 already does ship the correct Orgin and Label.

A workaround is to run apt update -y, but I'd rather not hardcode it in my scripts because of possibly security implications of accepting everything.

@francesco-ballarin
Copy link
Author

#1309 may offer an alternative way to fix this, but the change introduce in #1309 should be reverted anyways once the base image tag is upgraded to m112+, as allowing release info change would not be needed anymore.

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

2 participants