rkt/rkt

cat file into rkt run --interactive doesn't work

Open

#2,414 建立於 2016年4月13日

在 GitHub 查看
 (9 留言) (2 反應) (0 負責人)Go (8,871 star) (865 fork)batch import
component/stage0component/stage1help wantedkind/frictionpriority/P2

描述

I'd expect

cat file | rkt run --interactive --exec=cat to cat the file.

Instead it just hangs, waiting for stdin input. i.e. stdin isn't chained from the user who runs it to the container.

So for instance, in k8s we provide a python container to run python scripts that parse yaml files (and yaml file is cat into the running container). This works fine when the python container runtime is docker, but not when the same container image is used with rkt.

貢獻者指南

技術棧
go
領域
backendinfrastructure
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
basic understanding of container runtimesstdin piping
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
The issue is that piping input (e.g., cat file) to rkt run interactive does not forward stdin to the container. The expected behavior is that stdin from the host is passed to the container's process. To investigate, examine how rkt handles stdin in the interactive mode, specifically the code in stage1 or stage0 that sets up the container's stdin. Look at the source files in rkt/stage0/ or rkt/stage1/ for how the interactive flag is handled and how file descriptors are passed. Also check if there are any existing tests for interactive mode. The issue may be resolved by ensuring that the stdin file descriptor is properly connected from the host to the container's init process.