Hey folks, anyone have an example of running mirrord exec and starting a springboot appllication with gradle bootRun?

https://metalbear.co/guides/how-to-debug-a-java-microservice/ closest we have I think

Thanks for sharing mate. I was hitting some issues with the gradle daemon when executing via cli but starting the application from the IDE worked fine. 🙂

oh, you probably want to use

network.outgoing.ignore_localhost: true

so gradle can communicate safely

Hi all, we are hitting a weird issue where the command

mirrord exec -- /bin/bash

works in one namespace but not another, why is that? the error:

mirrord exec -- /bin/bash
New mirrord version available: 3.138.0. To update, run: `"brew upgrade metalbear-co/mirrord/mirrord"`.
To disable version checks, set env variable MIRRORD_CHECK_VERSION to 'false'.
* Running binary "/var/folders/xj/4xt3127542728_rxnc_z5b6r0000gn/T/mirrord-bin-ghu3278mz/bin/bash" with arguments: [].
* mirrord will run without a target, no configuration file was loaded
* operator: the operator will be used if possible
* env: all environment variables will be fetched
* fs: file operations will default to read only from the remote
* incoming: incoming traffic will be mirrored
* outgoing: forwarding is enabled on TCP and UDP
* dns: DNS will be resolved remotely
⠉ mirrord exec
    ✓ update to 3.138.0 available
  x mirrord exec
    ✓ update to 3.138.0 available
    ✓ ready to launch process
      ✓ layer extracted
      ✓ operator not found
      ✓ agent pod created
      ✓ pod is ready
      ✓ arm64 layer library extracted
    ✓ config summary                                                       Error:   × Failed to execute binary `/var/folders/
  │ xj/4xt3127542728_rxnc_z5b6r0000gn/T/mirrord-bin-ghu3278mz/bin/bash`
  │ with args ["/bin/bash"]

I can see the agent pod starts as expected with the pod log being "agent is ready"

amazing!

Folks, I got a nice working example with a hello-world type service. My next thing to understand is how to make this work in the context of a multi service call chain. Is this something mirrord supports?

Hi. I want usage mirrord in my cluster for demo to my command, but our security policy doesn’t allow pull image from different registry. I moved image to our registry, but I don’t see possibility to configure new image path. Is it possible?

I encountered the error: "mirrord process timed out" when trying to run the mirrord extension on IntelliJ. With the same setup, my colleague can run it without issues, but I get the above error. Could someone please help me with how to debug when using mirrord? Thank you!

hello mirrord people. I have a question: I have a windows 11 machine with wsl install with ubuntu 20.4 (kubectl available in both systems) in Goland from Intellij I have everyting setup to run in the windows environment. (not using wsl host machine) does mirrord works with this setup or I need to setup the "run environment" in wsl? from the IDE I have the error "can't use on Windows without WSL"

Hi, I am trying to use mirrord for my project and I am facing this issue. When I run:

mirrord exec --target pod/llm-7cb6646d5b-cmz45 --agent-namespace healthtech --target-namespace healthtech echo 123

or

mirrord exec --target deployment/llm --agent-namespace myns --target-namespace myns echo 123

I get following output:

mirrord exec
   ✓ running on latest (3.140.0)!
 ⠒ preparing to launch process
     ✓ layer extracted
⠉ mirrord exec
   ✓ running on latest (3.140.0)!
 ⠤ preparing to launch process
 ✓ layer extracted
 x mirrord exec
   ✓ running on latest (3.140.0)!
   x preparing to launch process
     ✓ layer extracted
     ✓ operator not found
     ✓ agent pod healthtech/mirrord-agent-bquydkyrt2-bbm2q created
     ✓ pod is ready
     Error:   × Failed to communicate with the agent: timeout

I've searched everywhere but couldn't find any solution. Even in this channel there are 4 threads with same issue but still could not find any solution. Can someone help me with this? The pod starts and is in running state for several seconds.

mirrord-agent-5q1rdfasxl-vrqvf   1/1     Running   0             5s

The only log I was able to find in the pod before it disappeared is:

agent ready - version 3.140.0

Hello, is it possible to both use a local container and IDE debugging or is it only for local processes ? Or even better debug a remote copy of the pod

Hi, I'm having this issue, attached the full log and the config file node:internal/process/promises:394 triggerUncaughtException(err, true /* fromPromise */); ^ Error: connect Unknown system error -111 127.0.0.1:4200 - Local (0.0.0.0:0) at internalConnect (node:net:1115:16) at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18) at node:net:1353:9 at process.processTicksAndRejections (node:internal/process/task_queues:85:11) { errno: -111, code: 'Unknown system error -111', syscall: 'connect', address: '127.0.0.1', port: 4200 } Any ideas on how to solve it? thanks. https://cdn.discordapp.com/attachments/950020257156833340/1367210380962693231/mirrord.json?ex=6813c164&is=68126fe4&hm=61adc1614c50197d00ccd4ca12faa0b37c6faafdef147525cb0c66a2d4206ebc& https://cdn.discordapp.com/attachments/950020257156833340/1367210381369409536/agent.log?ex=6813c164&is=68126fe4&hm=d5e221f096b2d5d9b42771137fc6f0b1e4f725e4c9ffe75057ae7c7618081f6d&

Has anyone had any luck with NextJS in VScode? Mirrord starts but it never reaches

npm dev -p 3001

* Running command: ./node_modules/.bin/next dev -p 3001
* mirrord will target: service/app-dev-service-dc961645, the configuration file was loaded from xxx
* mirrord will run without the mirrord Operator
* env: all remote environment variables will be fetched
* fs: file operations will default to read from the remote
* incoming: incoming traffic will be stolen
* outgoing: forwarding is enabled on TCP and UDP
* dns: DNS will be resolved remotely
* internal proxy: logs will be written to /var/folders/9w/mn_jvst936z08pnj1xsx0by40000gn/T/mirrord-intproxy-1746180472-zLPxJMa.log
⠄ mirrord exec
    ✓ running on latest (3.141.0)!
    ✓ ready to launch process
      ✓ layer extracted
      ✓ operator not found
      ✓ agent pod app-dev/mirrord-agent-kznolrogb1-hnvxt created
      ✓ pod is ready
      ✓ arm64 layer library extracted
    ✓ config summary

launch.json

{
  "type": "node",
  "request": "launch",
  "name": "Next.js: Debug with mirrord",
  "runtimeExecutable": "mirrord",
  "runtimeArgs": [
    "exec",
    "--config-file",
    "${workspaceFolder}/.mirrord/mirrord.json",
    "--"
  ],
  "program": "${workspaceFolder}/node_modules/.bin/next",
  "args": [
    "dev",
    "-p",
    "3001"
  ],
  "cwd": "${workspaceFolder}",
  "console": "integratedTerminal"
}

Hi, I'm trying to run mirrord extension from vscode and it fails. while running it from cli works without issues. it doesn't let me pick a pod and then complains on not being able to get pods from kubectl https://cdn.discordapp.com/attachments/950020257156833340/1369964721691951114/image.png?ex=681dc692&is=681c7512&hm=63d6061e0ea84b527a6f6c78fc8b0221d4424dbac8df9c317fbf30e2dcb81bad&

Hi, when using included ENV, mirrord didn't "take over" the target pod for example this case: "env": { "include": ["OTEL_NODE_DISABLED_INSTRUMENTATIONS"] }

Intelij IDE plugin

Anyone tried running mirrord with RustRover? For me even when mirrord is enabled, the application runs locally instead of mirroring

Hi, I am building a small stateful application using the ETCD raft protocol. I am wanting to use mirrord to speed up the development but am unable to do so due to file locks being created by my application. The application indicates that the wal log is already locked when trying to take over a pod. Is there maybe a way on how I could work around this or maybe restart the pod when trying to start the application?

message has been deleted

I am experimenting with mirrord, and I thought i understood a lot of how it works. Where I couldn't figure out is: How to use Workload Identity with this setup? I can see the workload identity token being injected into agent pod. Though the connection to other services i.e. Azure Storage Queues fail with Client Assertion. Wondering if there is anyone who has done setup where Workload Identity/ Service Account" have been used. { "target": { "path": "pod/app-dev-charts-api-95874f8d5-b72ws", "namespace": "app-dev" }, "feature": { "env": true, "fs": "read", "network": true }, "agent": { "log_level": "info", "labels": { "app": "workload", "azure.workload.identity/use": "true" }, "namespace": "app-dev", "service_account": "sa-app-dev" }, "kube_context": "au-aks-ctspoke-npd" }

Hi i'm try to use the vscode exetions for mirrord and get the following error 2025-05-20T08:24:03.524216Z ERROR mirrord::connection: error: mirrord operator API failed: creating a websocket connection failed with ApiError: Cannot find namespace

default

for targetless run.: 400 Bad Request (ErrorResponse { status: "Failure", message: "Cannot find namespace

default

for targetless run.", reason: "400 Bad Request", code: 400 }) at mirrord/cli/src/connection.rs:112 Error: × mirrord operator API failed: creating a websocket connection failed with │ ApiError: Cannot find namespace

default

for targetless run.: 400 Bad │ Request (ErrorResponse { status: "Failure", message: "Cannot find │ namespace

default

for targetless run.", reason: "400 Bad Request", code: │ 400 }) but i gave it a namespace this is my mirrord config { "feature": { "network": { "incoming": "mirror", "outgoing": true }, "fs": "read", "env": true }, "operator": false, "agent": { "namespace": "dev-amir-prompt" }, "target": { "namespace": "dev-amir-prompt" } }

Hello everyone. I'm trying to run mirrord with --steal towards a deployment with 2 replicas, but for some reason I only get some of the calls I make forwarded to the local process. In other words, If I run a sequence of

curl

requests to the remote endpoint, I only get about 1/2 of them in my local service. Can it be because the deployment has 2 replicas? This is how I run mirrord

mirrord exec --steal --no-remote-dns --no-outgoing --agent-log-level debug -n <my namespace> -a <my namespace> --target deployment/<my deployment>/container/<my container> -- <my command here>

I am not able to make it work on rustrover. The intelij plugin does not show the prompt to select the pod.

How to fix it ?

Is there any way to silence the output from mirrord? Or only extract the actual command output?

Hi there, we’re facing an issue where some developers (that are using a mac m3 with 16GB of RAM) are stuck in the project start process when running debug with Mirrod. If we disable the Mirrod extension, the issue goes away. Do you have any ideas on how to resolve this?

Hi, I have been trying to resolve some issues where connection drops. I have had limited success by doing this - https://metalbear.co/mirrord/docs/faq/common-issues#agent-connection-fails-or-drops-when-using-an-ephemeral-agent-with-a-service-mesh The first time it works, but the second time I get this.

{
  "timestamp": "2025-07-18T05:54:45.794723Z",
  "level": "ERROR",
  "fields": {
    "error": "io error: Address already in use (os error 98)"
  },
  "target": "mirrord_agent::entrypoint",
  "span": {
    "args": "Args { mode: Ephemeral { mesh: None }, communicate_port: 51234, communication_timeout: 360, network_interface: None, metrics: None, test_error: false, operator_tls_cert_pem: None, is_mesh: true, ipv6: false }",
    "name": "start_agent"
  },
  "spans": [
    {
      "args": "Args { mode: Ephemeral { mesh: None }, communicate_port: 51234, communication_timeout: 360, network_interface: None, metrics: None, test_error: false, operator_tls_cert_pem: None, is_mesh: true, ipv6: false }",
      "name": "start_agent"
    }
  ],
  "threadId": "ThreadId(1)"
}

I don't have

ttl

set, but I do have

communication_timeout: 360
      startup_timeout: 360

Will these keep the agent alive? Or is there a recommended way to make this work? Thanks

Hey, me again. I don't think this is the same issue but similar to above. The first time a pod boots up, mirrord works. After the second time I try to connect, it logs something about IP tables, I'll post in thread. There is still another agent Running in the pod according to k8. However said running agent has logged several close messages, so I'm confused why it's still running.