nt
commented
3 hours ago I was able to repro in a virtualbox (no containerd) running ubuntu/jammy:
vboxuser@Ubuntu:~$ runsc -version
runsc version release-20241007.0
spec: 1.1.0-rc.1
vboxuser@Ubuntu:~$ uname -a
Linux Ubuntu 6.8.0-40-generic #40~22.04.3-Ubuntu SMP PREEMPT_DYNAMIC Tue Jul 30 17:53:10 UTC 2 aarch64 aarch64 aarch64 GNU/Linux
Description
We run
nc -l 7777in a gvisor container and are not able to connect to it using port-forwarding.runsc-fails-to-port-forward.log
Steps to reproduce
I produced the logs by running:
sudo ~/runsc -network=sandbox -debug --alsologtostderr -overlay2=all:memory run nt-test28 2>&1 | sudo tee runsc-fails-to-port-forward.logsudo ~/runsc port-forward nt-test28 7777:7777wget http://0.0.0.0:7777/runsc version
runsc version release-20241007.0 spec: 1.1.0-rc.1
(I tried a more recent version but ran into this issue https://github.com/google/gvisor/issues/10944
Note: we run this from whithin a containerd container.
docker version (if using docker)
No response
uname
Linux nt-test-sandboxing-77dd9dfb8f-w79m7 5.10.213-201.855.amzn2.x86_64 #1 SMP Mon Mar 25 18:16:11 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
kubectl (if using Kubernetes)
Client Version: v1.29.3 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.30.3-eks-a18cd3a
repo state (if built from source)
No response
runsc debug logs (if available)
No response