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

Ubuntu Latest Version: 20210309.1 cannot find Release file #2938

Closed
1 of 7 tasks
stevepiercy opened this issue Mar 15, 2021 · 4 comments
Closed
1 of 7 tasks

Ubuntu Latest Version: 20210309.1 cannot find Release file #2938

stevepiercy opened this issue Mar 15, 2021 · 4 comments
Assignees
Labels
Area: Containers investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: Ubuntu

Comments

@stevepiercy
Copy link

stevepiercy commented Mar 15, 2021

Description
A new error message started appearing today in repos under the Pylons organization.

From:

https://github.com/Pylons/deformdemo/runs/2114011815?check_suite_focus=true#step:5:60

E: The repository 'https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  Release' no longer has a Release file.

Virtual environments affected

  • Ubuntu 16.04
  • Ubuntu 18.04
  • Ubuntu 20.04
  • macOS 10.15
  • macOS 11.0
  • Windows Server 2016 R2
  • Windows Server 2019

Image version

Version: 20210309.1

@jackgerrits
Copy link

I am hitting this also hitting this here: https://github.com/VowpalWabbit/vowpal_wabbit/runs/2113958668

Current runner version: '2.277.1'
Operating System
  Ubuntu
  20.04.2
  LTS
Virtual Environment
  Environment: ubuntu-20.04
  Version: 20210309.1
  Included Software: https://github.com/actions/virtual-environments/blob/ubuntu20/20210309.1/images/linux/Ubuntu2004-README.md
  Image Release: https://github.com/actions/virtual-environments/releases/tag/ubuntu20%2F

@sirosen
Copy link

sirosen commented Mar 15, 2021

To share a workaround while we wait for a fix, here's what I'm doing:

sudo rm /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list
sudo apt-get update -y

Looks like this is how GitHub installs podman onto the VMs:
https://github.com/actions/virtual-environments/blob/1ef3339658fcf902799dfe6c55a8b75d359c19ae/images/linux/scripts/installers/containers.sh

So it's unlikely that most people doing builds need to update these packages. I don't know whether or not it's a good idea for the VMs to still have these sources in place after the machine is built? On the one hand, it makes the VM more internally consistent (because we can see where the installed packages came from). On the other hand, it exposes users to potential upstream breakage. Maybe the VM build should run a sed -i 's/^/#/' on this, so an ordinary user doing an apt update can't be broken by this.

@dibir-magomedsaygitov dibir-magomedsaygitov added OS: Ubuntu Area: Containers investigate Collect additional information, like space on disk, other tool incompatibilities etc. and removed needs triage labels Mar 15, 2021
@al-cheb
Copy link
Contributor

al-cheb commented Mar 15, 2021

Hello, @stevepiercy
Release file was updated in the repo and I unable to reproduce the issue:
image
image

@al-cheb
Copy link
Contributor

al-cheb commented Mar 15, 2021

Close as duplicate #2919.

@al-cheb al-cheb closed this as completed Mar 15, 2021
@sirosen sirosen mentioned this issue Mar 15, 2021
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Containers investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: Ubuntu
Projects
None yet
Development

No branches or pull requests

5 participants