firecracker-microvm / firecracker-microvm/firecracker-containerd

Should the container rootfs take the input Type instead of hardcoding ext4?

Open
#824 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.9k
Forks
247
PR merge metrics
No merged PRs in 30d

Description

https://github.com/firecracker-microvm/firecracker-containerd/blob/e6c7a36c34f827a4229d4c898f9b406e9742d7a5/runtime/service.go#L1186

I'm specifically interested in supporting XFS-based snapshots for the container rootfs. I know other drives can be XFS, is there a reason that the container rootfs has to be ext4? (Assume I build my kernel with XFS support)

Thanks!

Contributor guide

Open the contributing guide

Research direction

Start at runtime/service.go around line 1186 and trace how the container rootfs type is selected and passed into the service. Check the existing rootfs and snapshot handling, then determine what behavior and tests would demonstrate support for XFS-based snapshots instead of a hardcoded ext4 type.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.