port forwarding failing from container to local

[gophalgun]

What happened?
devspace --debug dev

Noticed port started log:
11:23:26 dev:myapp ports Port forwarding started on: 8000 -> 8000

After trying to load webpage on http://localhost:8000/, it fails and notice corresponding new error logs:

11:26:56 dev:myapp ports Restarting because: error creating forwarding stream for port 8000 -> 8000: Timeout occurred
11:26:57 dev:myapp ports Start selecting a single pod with selector pod name: myapp-6787794dd-l49hg
11:26:58 dev:myapp ports Port forwarding started on: 8000 -> 8000

This cycle gets repeated, as I try to access the webpage by reloading.
Logging in with VSCode dev containers extension into container and forwarding port that way helps and I can access webapp on same address.
Activity Monitor on mac -> inspect "devspace" process -> "Open Files and Ports" tab does not show 8000 being opened at any point in this whole duration.

What did you expect to happen instead?
Webpage should be loading on 8000 with devspace, no errors in logs.

How can we reproduce the bug? (as minimally and precisely as possible)
My devspace.yaml:

version: v2beta1
name: my-internal-apps
...
dev:
  myapp:
    imageSelector: myapp-image
    ports:
      - port: 8000:8000

Local Environment:

• DevSpace Version:

$ devspace version
DevSpace version : 6.3.15

• Operating System: mac
• ARCH of the OS: ARM64
  Kubernetes Cluster:
• Cloud Provider: other - single node manually installed k8s cluster
• Kubernetes Version:

kubectl version
Client Version: v1.33.1
Kustomize Version: v5.6.0
Server Version: v1.33.0

Anything else we need to know?
Issue can be reproduced on linux connected to same cluster and docker daemon

[zerbitx]

Just to check, have you tried using another local port, like 8123:8000?

[gophalgun]

Hi, thanks for the reply. This is not a bug on devspace tool, it's fixed from my end.

After further debugging using other ways of port forwarding like kubectl port-forward, I have found out the socat is missing on my node. After installing it the problem got solved.