Sascha Grunert

/override ci/prow/e2e-agnostic /override ci/prow/e2e-gcp /override ci/prow/images

Thank you for the issue report @afazekas! Hm, so a `kubectl exec -it` should result in something like this in the logs: ``` DEBU[…] Request: &ExecRequest{ContainerId:1293ee29666010f3a4c94a614b64f31d773f72919629fe12396620ecd2f64271,Cmd:[echo hi],Tty:true,Stdin:true,Stdout:true,Stderr:false,} file="otel-collector/interceptors.go:63" id=1ea0bbf9-4cbf-46d1-973e-effa346decea name=/runtime.v1.RuntimeService/Exec...

Checking slack support from actuated in https://self-actuated.slack.com/archives/C043BB2NCUW/p1721206076124419

So, I can reproduce the issue using the branch [ping-arm64](https://github.com/cri-o/cri-o/tree/ping-arm64), but everything seems to be fine: IPv6 is enabled, sysctl seems to be right. I still cannot ping using IPv6,...

Yes, here is the output from `ping6 -c1 1100:200::3` (from pod 1 to pod 2): https://gist.github.com/saschagrunert/e5661341df7857bee67c11a4ddce7394 dmesg (last interesting lines): ``` [ +0.001280] systemd[1]: Started Journal Service. [ +0.013014] systemd-journald[831]:...

The containers already run privileged, so I assume it's not a permission problem.

@kwilczynski yes so pinging the same address works: ``` bash-5.2# ping6 ip6-localhost ping6: ip6-localhost: Name or service not known bash-5.2# ping6 localhost6 PING localhost6(localhost (::1)) 56 data bytes 64 bytes...

Closing this issue now, since it's related to a test setup we don't have anymore.

I see the same issue with Podman 4.7: ``` Copying blob 21b98c2cb85e [========>-----------------------------] 25.0MiB / 100.0MiB | 1.3 GiB/s ``` I think we introduced the change in https://github.com/containers/image/pull/2015. Since `pull`...

Unfortunately I had no further time spent on this. @mtrmac do you have a rough guess where the issue may come from?