Failed at mounting volume

[keyolk]

Describe the bug
It fails taking volume from the replicaset,
with --mount false it works.
Any clue to resolve this?

my setup env

$ telepresence helm install --set trafficManager.serviceMesh.type=istio
$ telepresence connect -n soda --docker

reproduction process

$ telepresence intercept api-zone-c-5d546b9b78 --port 80:80 --container api-0 --docker-run -- nginx
Using ReplicaSet api-zone-c-5d546b9b78
   Intercept name         : api-zone-c-5d546b9b78
   State                  : ACTIVE
   Workload kind          : ReplicaSet
   Destination            : 127.0.0.1:80
   Service Port Identifier: http-80/TCP
   Intercepting           : all TCP connections
docker: Error response from daemon: error while mounting volume '': get api-0-5: no such volume.

telepresence log
telepresence_logs.zip

Expected behavior
Able to intercept the workload

Versions (please complete the following information):

using m1 macbook with docker desktop

$ telepresence version
OSS Client             : v2.21.2
OSS Daemon in container: v2.21.2
OSS Traffic Manager    : v2.21.2
Traffic Agent          : ghcr.io/telepresenceio/tel2:2.21.2
$ kubectl version
Client Version: v1.30.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.8-eks-2d5f260
$ istioctl version
no ready Istio pods in "istio-system"
1.22.0

Additional context

• no rollouts printed from the list command only replicaset and pods
• intercepting working well with simple deployment which has configmaps and secrets

[thallgren]

Can you please provide the logs with loglevel debug? It would also be interesting to see the volumes and volume mounts in the replicaset.

[thallgren]

Ah, sorry. You had debuglevel turned on further down.

[thallgren]

Also, please note that the OSS version of Telepresence have no support for the serviceMesh Helm value. Valid Helm settings can be found here.

[keyolk]

@thallgren Thx, then what is the recommended way to use telepresence with istio environment? using ambassador telepresence ?