Ubuntu-20.04 Runner for Magma

[tapasmishra]

Select Topic Area

Question

Body

Hi there,

Magma is an open-source software platform that provides network operators with a flexible and extensible mobile core network solution. Most Magma actions depend on Ubuntu 20.04. However, with Ubuntu 20.04 runners no longer available, all actions are now stuck in a pending state due to the lack of available runners. Since this repository is community-driven, migrating away from the Ubuntu 20.04 dependency will take a few months. Is there any possibility of making an Ubuntu 20.04 runner available for the next couple of months?

Regards,
Tapas

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[HoeunPichet]

To use an Ubuntu-20.04 runner for Magma, you can simply specify it in your GitHub Actions workflow like this:
runs-on: ubuntu-20.04

This tells GitHub to use a hosted runner with Ubuntu 20.04, which is compatible with Magma’s build requirements (like for AGW or NMS). Here's a basic example:

jobs:
  build:
    runs-on: ubuntu-20.04
    steps:
      - uses: actions/checkout@v3
      - run: sudo apt-get update && sudo apt-get install -y docker docker-compose
      - run: |
          cd lte/gateway
          make build_oai

If you need more customization or longer build times, you can also set up a self-hosted runner on an Ubuntu 20.04 machine.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[RamprakashRP]

There isn't a direct way for a user to request a specific, deprecated runner image like Ubuntu 20.04 to be made available for a GitHub repository. GitHub's policy is to retire older runner images and focus on providing and maintaining current, secure versions. The best course of action is to migrate your workflows to a supported runner image, such as Ubuntu 22.04.

Why Deprecated Runners Aren't Reinstated
GitHub manages a large fleet of virtual machines for its runners. Maintaining and securing older images like Ubuntu 20.04 is resource-intensive and can pose security risks. By retiring them, GitHub can ensure that all runners are up-to-date with the latest security patches and software.

Recommended Actions
Since your repository is community-driven and a full migration will take time, here are a few options you can explore:

Self-Hosted Runners: You can set up your own self-hosted runner on a machine running Ubuntu 20.04. This involves installing the GitHub Actions runner application on your own server or virtual machine. This gives you complete control over the environment and would allow you to continue using your existing workflows while the community works on migrating.

Use the Closest Supported Version: Try updating your workflows to use ubuntu-latest or ubuntu-22.04. While this may cause some dependency issues, it could also reveal that many of your actions are already compatible. This could be a faster solution than you think.

Request an Exception (Unlikely): While you can open a support ticket with GitHub, it's highly unlikely they will reinstate a retired runner image. They may, however, be able to provide guidance or suggest alternative solutions specific to your project.