Google maintains mirrors of the Debian apt repos at:
https://packages.cloud.google.com/mirror/cloud-apt
I have these entries in my sources:
deb https://packages.cloud.google.com/mirror/cloud-apt/buster buster main
deb https://packages.cloud.google.com/mirror/cloud-apt/buster-security buster-security main
deb https://packages.cloud.google.com/mirror/cloud-apt/buster-updates buster-updates main
deb https://packages.cloud.google.com/mirror/cloud-apt/buster-backports buster-backports main
The first one "buster" works fine.
The other three "buster-security", "buster-updates" and "buster-backports" all return 404 not found.
The instance in question does not have http/https egress to the rest of the internet so I can't use the Debian repos.
Can anyone explain where the other repos have gone, or have some better advice as to the correct entries for sources.list?
Hi @bench_up,
Welcome to the Google Cloud Community!
As a workaround, you may try creating a repository in Artifact Registry, add the package to the repository, then install it into the VM.
First, you need to enable Private Google access - Configure Private Google Access.
Then, you may follow the steps provided in this documentations:
I hope this helps. Thank you.
Thank you for your response. Of course your solution is OK for one package but in order to solve the problem, I'd have to mirror the entire of 3 Debian repos.
Can you confirm if there is a problem that can be fixed or will these 3 repo URLs 404 forever intentionally?
https://packages.cloud.google.com/mirror/cloud-apt/buster-security
https://packages.cloud.google.com/mirror/cloud-apt/buster-updates
https://packages.cloud.google.com/mirror/cloud-apt/buster-backports
Thanks.