google/gvisor

Implement /dev/kmsg inside gVisor

Open

#2,290 建立於 2020年3月31日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)Go (12,713 star) (1,061 fork)batch import
area: compatibilityarea: filesystemgood first issuestatus: help wantedtype: enhancement

描述

I am trying to run ltp(https://github.com/linux-test-project), while it seems to run fine with runc in the docker privileged mode. I am getting error when I do the same with runsc.

image

Basically, ltp needs access to /dev/kmsg which I enabled in runc by running it with --privileged flag but the same is not working with runsc-kvm. I know runsc have stricter boundaries when it comes to giving access. I was wondering is there any way I can disable this in the build or by any other way?

貢獻者指南

技術棧
go
領域
infrastructurecloud
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Understanding of gVisor architectureLinux kernel device modelGo programming
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
Investigate how gVisor currently handles virtual devices like /dev/null or /dev/console. The implementation likely requires adding a new kernel device in the sentry codebase (e.g., in pkg/sentry/devices/). Review existing device implementations and the LTP test suite requirements for /dev/kmsg. Check the gVisor documentation and any prior discussions in the issue comments for design constraints.