Open ssplatt opened 6 hours ago
I'm in a similar situation. My azure pipeline which starts a docker image as part of some unit tests was working fine on version 20240908.1.0
but stopped working on 20240915.1.0
.
Hey!
I also encountered this problem after updating the images to 20240915.1.0
.
On images 20240908.1.0
all was fine.
Description
Starting September 18, my Virtualbox image builds have failed with the initial configuration being left in 'gurumeditation' state. I tried updating Virtualbox, Vagrant, Packer, and all underlying software in the build script but none of it worked. I believe the issue is due to the kernel and/or hypervisor configuration in the Github Actions runner itself.
Platforms affected
Runner images affected
Image version and build link
Current runner version: '2.319.1' Operating System Ubuntu 22.04.5 LTS Runner Image Image: ubuntu-22.04 Version: 20240915.1.0 Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240915.1/images/ubuntu/Ubuntu2204-Readme.md Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240915.1 Runner Image Provisioner 2.0.384.1 GITHUB_TOKEN Permissions Contents: read Metadata: read Packages: read
https://github.com/ssplatt/vagrant-box-centos-stream-9/actions/runs/10933205667/job/30351289562
Is it regression?
https://github.com/ssplatt/vagrant-box-centos-stream-9/actions/runs/10914285276
Expected behavior
virtual machine starts, runs, builds, and shuts down.
last good build:
Actual behavior
Repro steps
start build, fail.