You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey everyone,
I have an issue where the exec process hangs when I'm piping the input: echo 123 | sudo firecracker-ctr --address /run/firecracker-containerd/containerd.sock tasks exec --exec-id test test cat
I experienced this issue for the first time when I was playing around with firecracker-containerd through API and it seems it's a broader issue. I've also double checked and latest version of containerd with runc doesn't have similar issues.
sudo firecracker-ctr --address /run/firecracker-containerd/containerd.sock \
run \
--snapshotter devmapper \
--runtime aws.firecracker \
--rm --tty --net-host \
docker.io/library/debian:latest \
test
echo 123 | sudo firecracker-ctr --address /run/firecracker-containerd/containerd.sock tasks exec --exec-id test test cat
5. Process will echo "123" and hang
Note
I tried to make it as easy to reproduce as possible but in general we're experiencing the same issue on the broader scale internally.
The text was updated successfully, but these errors were encountered:
Hey everyone,
I have an issue where the exec process hangs when I'm piping the input:
echo 123 | sudo firecracker-ctr --address /run/firecracker-containerd/containerd.sock tasks exec --exec-id test test cat
I experienced this issue for the first time when I was playing around with firecracker-containerd through API and it seems it's a broader issue. I've also double checked and latest version of containerd with runc doesn't have similar issues.
pprof
After running firecracker-ctr exec
Firecracker Logs
After running firecracker-ctr exec
After killing the firecracker-ctr exec process
Steps to reproduce
echo 123 | sudo firecracker-ctr --address /run/firecracker-containerd/containerd.sock tasks exec --exec-id test test cat
5. Process will echo "123" and hang
Note
I tried to make it as easy to reproduce as possible but in general we're experiencing the same issue on the broader scale internally.
The text was updated successfully, but these errors were encountered: