Repository navigation
The Ubuntu 18.04 Actions runner image will begin deprecation on 2022/08/08 and will be fully unsupported by 2023/04/03Β #6002
Description
Breaking changes
We have started the deprecation process for Ubuntu 18.04. While the image is being deprecated, You may experience longer queue times during peak usage hours. Deprecation will begin on 2022/08/08 and the image will be fully unsupported by 2023/04/03
To raise awareness of the upcoming removal, we will temporarily fail jobs using Ubuntu 18.04. Builds that are scheduled to run during the brownout periods will fail. The brownouts are scheduled for the following dates and times:
GitHub Actions\Azure DevOps::
- October 3, 12:00 UTC β October 3, 14:00 UTC
- October 18, 14:00 UTC β October 18, 16:00 UTC
- November 15, 18:00 UTC β November 15, 20:00 UTC
- November 30, 20:00 UTC β November 30, 22:00 UTC
- December 15, 20:00 UTC β December 16 00:00 UTC
- January 5, 10.00 UTC β January 5, 14.00 UTC
- January 13, 12.00 UTC β January 13, 16.00 UTC
- January 18, 14.00 UTC β January 18, 18.00 UTC
- January 24, 16.00 UTC β January 24, 20.00 UTC
- February 7, 16.00 UTC β February 7, 22.00 UTC
- February 21, 10.00 UTC β February 21, 22.00 UTC
- March 6, 00.00 UTC β March 7, 00.00 UTC
- March 13, 00.00 UTC β March 14, 00.00 UTC
- March 21, 00.00 UTC β March 22, 00.00 UTC
- March 28, 00.00 UTC β March 29, 00.00 UTC
Target date
April 1st, 2023
The motivation for the changes
We maintain the latest two stable versions of any given OS version. Ubuntu 22.04 is going GA on 8/8/22 thus we start deprecating the oldest image.
Possible impact
Workflows using the ubuntu-18.04 image label should be updated to ubuntu-latest, ubuntu-20.04, or ubuntu-22.04
Platforms affected
- Azure DevOps
- GitHub Actions
Virtual environments affected
- Ubuntu 18.04
- Ubuntu 20.04
- Ubuntu 22.04
- macOS 10.15
- macOS 11
- macOS 12
- Windows Server 2019
- Windows Server 2022
Mitigation ways
N\A
Activity
willaaam commentedon Aug 8, 2022
Don't get me wrong, I fully understand that you're deprecating 18.04 - but incorporating brownout periods to raise awareness?
If my team needs to get a build out for a critical bugfix on the 22nd of August... I'm just going to have to wait for 4 hours? If my understanding of that is true, I find that very odd behavior in an enterprise environment. Some businesses actually have SLAs with their clients. Would kindly request the team to find another way to "raise awareness". I came here because of the red banner when using the image, that worked fine as well and is a lot less invasive.
You're giving us two weeks to migrate away before brownouts start. Migrating is an action that requires testing and validation.
Bump ubuntu to 22.04
Bump ubuntu to 20.04
Bump ubuntu to 20.04
Bump ubuntu to 20.04
Bump ubuntu to 20.04 (#12062)
fbrosseau commentedon Aug 8, 2022
Does this impact hosted agents only, or does this also mean the agent tooling/infra (for self hosted pools, but also for 1ES pools for internal folks) will become EOL for ubuntu18? My team still needs to keep shipping ubuntu18 versions of our product for years.
Use `ubuntu-20.04` build environment
github: Move CI to ubuntu 20.04 base image.
CI: Azure: Move to Ubuntu 22.04 image
panekj commentedon Aug 8, 2022
@fbrosseau it's hosted agent only
Actions: remove Ubuntu 18.04 runner
253 remaining items
aligajani commentedon Feb 7, 2023
I do not think it is a good idea to prevent Github actions from running due to a brownout. You could notify us in a different way, or warn us using some alerts, but preventing a critical push due to this issue isn't a pleasing Developer Experience.
joshforbes commentedon Feb 7, 2023
I do not think a "brownout" is a good strategy for this. Quite frustrating to be honest. We don't want to move off of 18.04, our plan is to move to a container before the deadline. However, it would have been nice to continue operations uninterrupted until the date.
AleksandarTokarev commentedon Feb 7, 2023
I agree with the comments above - brownouts are not the best way to do things - it would be better to have notifications or emails sent with warnings instead.
probonopd commentedon Mar 5, 2023
Will it become un_supported_ or un_available_? I hope the former, since I'd like to continue building for it.
CALIFAS95 commentedon Mar 6, 2023
dirkf commentedon Mar 6, 2023
How do we run tests against old versions of packages not offered in later Ubuntu images?
kyrofa commentedon Mar 6, 2023
Consider using docker, @dirkf.
GKOLKO commentedon Mar 7, 2023
Hello, I am facing issue with the new versions of Ubunto (20, 22 and latest)
I have this error each time: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.3.0:resources (default-resources) on project ebx-technip-module: filtering /home/vsts/work/1/s/mdm-technip/ebx-technip-module/src/main/resources/resources.lnk to /home/vsts/work/1/s/mdm-technip/ebx-technip-module/src/main/webapp/WEB-INF/classes/resources.lnk failed with MalformedInputException: Input length = 1 -> [Help 1]
How can I solve this issue?
MikeMcC399 commentedon Mar 7, 2023
@GKOLKO
This does not sound like an error with the GitHub runner. I suggest you search instead on https://stackoverflow.com/.
nahimmedvent commentedon Mar 23, 2023
Ubuntu 20.04 and 22.04 don't work at all for me, I keep getting the error /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/site/wwwroot/.python_packages/lib/site-packages/pyodbc.cpython-37m-x86_64-linux-gnu.so)
Because these versions run on 2.29 glibc
mikhailkoliada commentedon Mar 24, 2023
@nahimmedvent software on Ubuntu 20.04 and 22.04 is compiled with newer version of libc, which makes the software compiled with older version of libs simply incompatible. There is no straightforward way tp solve this problem as it is a bit non-trivial. The easiest solution would be to switch to ubuntu:18.04 in docker.
lakshyaelite commentedon Mar 29, 2023
This will happen on April fools π€£
mikhailkoliada commentedon Apr 3, 2023
Ubuntu-18.04 is deprecated and disabled for all the customers
Abduljakulsalsal commentedon Apr 7, 2023
βοΈ
eyalroz commentedon Apr 16, 2023
Well, you could at least provide a proper notice about Ubuntu 18.04 runners no longer being available, instead of having actions fail mysteriously...