Skip to content

Updated Firecracker Version to 1.12.1 #11627

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 30, 2025
Merged

Updated Firecracker Version to 1.12.1 #11627

merged 1 commit into from
Jul 30, 2025

Conversation

itsmohitnarayan
Copy link
Contributor

@itsmohitnarayan itsmohitnarayan commented Jul 27, 2025 •
edited
Loading

This PR updates the Firecracker version bundled with Kata Containers from v1.8.0 to the latest stable v1.12.1.

Summary of Changes

  • Updated versions.yaml to point to Firecracker v1.12.1

Verification & Testing on VPS

🔧 Binary Version Check

/opt/kata/bin/firecracker --version
# Output:
Firecracker v1.12.1

/opt/kata/bin/jailer --version
# Output:
jailer v1.12.1

Functional Validation with Kubernetes On VPS

  • Deployed 5 pods using kata-fc runtime class and gitpod/openvscode-server:latest container.
  • All pods launched successfully and were in Running state.
  • Verified container access, resource allocation, and proper Firecracker usage.
kubectl get pods
# All pods showed STATUS=Running

kubectl exec -it vscode-kata-1 -- uname -a
# Output showed kernel running inside the microVM

ps aux | grep firecracker
# Verified that Firecracker process was running

Example Pod Description (vscode-kata-1)

  • RuntimeClass: kata-fc
  • Container image: gitpod/openvscode-server:latest
  • Memory limit: 1Gi, CPU: 1
  • Kernel: Linux 6.12.36 inside microVM
  • Pod scheduled and initialized correctly
  • Replaced both firecracker and jailer binaries under /opt/kata/bin
    and tested if its able to create microvm

Ready for Review

The Process is tested on a VPS and ready for review. Please let me know if you'd like any additional tests or modifications.

@fidencio fidencio requested review from ananos and fidencio July 27, 2025 21:56
@fidencio
Copy link
Member

Let's have the tests running! :-)
Thanks for your (first of many?) contributions, @itsmohitnarayan!

@fidencio
Copy link
Member

Commit Messae Check test failed: https://github.com/kata-containers/kata-containers/actions/runs/16549167931/job/46817238946?pr=11627

Your commit message should follow a structure, something like:

versions: Upgrade to Cloud Hypervisor v47.0

Details of v47.0 release can be found in our roadmap project as
iteration v47.0: https://github.com/orgs/cloud-hypervisor/projects/6.

Signed-off-by: ...

@fidencio
Copy link
Member

For now, let the tests run before updating the commit message, as we can check whether the update passes on all our tests or not.

@itsmohitnarayan
Copy link
Contributor Author

Commit Messae Check test failed: https://github.com/kata-containers/kata-containers/actions/runs/16549167931/job/46817238946?pr=11627

Your commit message should follow a structure, something like:

versions: Upgrade to Cloud Hypervisor v47.0

Details of v47.0 release can be found in our roadmap project as
iteration v47.0: https://github.com/orgs/cloud-hypervisor/projects/6.

Signed-off-by: ...

I'm Really Sorry, I was not aware of it.

RuoqingHe
RuoqingHe reviewed Jul 28, 2025
View reviewed changes
Copy link
Member

@RuoqingHe RuoqingHe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You may amend your PR with git commit --amend -s, and organize your commit title and body like @fidencio suggested 🙂

@itsmohitnarayan
Copy link
Contributor Author

You may amend your PR with git commit --amend -s, and organize your commit title and body like @fidencio suggested 🙂

Yes @RuoqingHe I'll change it, I was just waiting because findencio suggested to wait for the tests results.

@fidencio
Copy link
Member

Yes @RuoqingHe I'll change it, I was just waiting because findencio suggested to wait for the tests results.

Tests passed, feel free to adjust the commit message :-)

@itsmohitnarayan
versions: Upgrade Firecracker Version to 1.12.1
5cccbb9 
Updated versions.yaml to use Firecracker v1.12.1.
Replaced firecracker and jailer binaries under /opt/kata/bin.

Tested with kata-fc runtime on Kubernetes:
- Deployed pods using gitpod/openvscode-server
- Verified microVM startup, container access, and Firecracker usage
- Confirmed Firecracker and jailer versions via CLI

Signed-off-by: Kumar Mohit <68772712+itsmohitnarayan@users.noreply.github.com>
@itsmohitnarayan itsmohitnarayan force-pushed the FirecrackerVersionUpdate branch from 99f3317 to 5cccbb9 Compare July 30, 2025 07:21
fidencio
fidencio approved these changes Jul 30, 2025
View reviewed changes
Copy link
Member

@fidencio fidencio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thanks @itsmohitnarayan!

ananos
ananos approved these changes Jul 30, 2025
View reviewed changes
Copy link
Member

@ananos ananos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @itsmohitnarayan!

@ananos ananos merged commit 00e0db9 into kata-containers:main Jul 30, 2025
338 of 357 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@RuoqingHe RuoqingHe RuoqingHe left review comments

@fidencio fidencio fidencio approved these changes

@ananos ananos ananos approved these changes

Assignees
No one assigned
Labels
ok-to-test
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@itsmohitnarayan @fidencio @ananos @RuoqingHe