You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
#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.
Running
apt update
inside a current kaggle docker image givesCan you considering updating the base image from tag
m111
to a later one? For instance,m112
already does ship the correctOrgin
andLabel
.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.The text was updated successfully, but these errors were encountered: