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.