Error: An image label with the label Ubuntu22 does not exist.
See original GitHub issueDescribe the bug
No longer able to run jobs on ubuntu-latest
.
To Reproduce Steps to reproduce the behavior:
- Run a job on
ubuntu-latest
- Job is automatically cancelled with error “An image label with the label Ubuntu22 does not exist.”
Expected behavior Job runs normally, as it did previously.
Runner Version and Platform
Current runner version: ‘2.304.0’
OS of the machine running the runner? OSX/Windows/Linux/… Linux (Ubuntu)
What’s not working?
Please include error messages and screenshots.
An image label with the label Ubuntu22 does not exist.
Job Log Output
This job was cancelled
Issue Analytics
- State:
- Created 3 months ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
An image label with the label Ubuntu16 does not exist
##[warning]An image label with the label Ubuntu16 does not exist. ,##[error]The remote provider was unable to process the request.
Read more >GIT Tag step- cancelled in the build - azure pipelines
##[warning]An image label with the label Ubuntu16 does not exist. ,##[error]The remote provider was unable to process the request.
Read more >Updates to hosted pipelines images.
With this update, we are announcing updates to hosted pipelines images. The Ubuntu 22.04 image is now generally available, this is the ...
Read more >How to fix this error [error]The remote provider was unable ...
Please check the following things: 1. Ensure that the image label you are using is correct. 2. Ensure that the image you are...
Read more >GitHub Actions: Ubuntu 22.04 is now generally available ...
The Ubuntu 18.04 Actions runner image started our deprecation process on 8/8/22 and will be fully unsupported by 12/1/22. To raise awareness of ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah yes, this issue has been resolved. Just paused the CI for a few days and then everything went back to normal. Thanks for following up!
Seems to be due to actions/runner-images#7660