google/gvisor

Implement /dev/kmsg inside gVisor

Open

#2,290 opened on Mar 31, 2020

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (1,061 forks)batch import
area: compatibilityarea: filesystemgood first issuestatus: help wantedtype: enhancement

Repository metrics

Stars
 (12,713 stars)
PR merge metrics
 (Avg merge 6d 13h) (156 merged PRs in 30d)

Description

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?

Contributor guide

Research direction
Understand the gVisor device framework and implement /dev/kmsg (a character device for kernel messages) similar to how other devices like /dev/null are implemented. Trace the LTP test that requires /dev/kmsg.
Tech stack
go
Domain
backendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoLinux kernel
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20