t4lz

When doing this change, we can also change the `mirrord ls` code in the cli to also list container targets for deployments and argo rollouts, not only for pods. The...

Another note: in the non-operator code of `mirrord ls`, the containers are filtered by name: https://github.com/metalbear-co/mirrord/blob/e92c20d2d117170c3186799f8c7cdafb615779b4/mirrord/cli/src/main.rs#L270 The same filter should be performed after fetching the target list from the operator,...

https://github.com/metalbear-co/mirrord/pull/2437

Wouldn't `mirrord exec -f .miorrord/mirrord.json docker -- run my-image` work?

Got it, thanks. With unix sockets it could communicate with the docker engine on the cluster and run it there, right?. Maybe that's useful too?

Tried to check if this still happens and encountered a new error: ``` Error: × SIP Error: `Sign( │ 256, │ "/var/folders/4l/810mmn597cx7zy5w2bk11clh0000gn/T/mirrord-bin/Applications/pgAdmin 4.app/Contents/MacOS/pgAdmin 4: replacing existing signature\n/var/folders/4l/810mmn597cx7zy5w2bk11clh0000gn/T/mirrord-bin/Applications/pgAdmin 4.app/Contents/MacOS/pgAdmin 4: bundle...

Update: when running again I don't get the new error, but I do get the first error described in this issue.

The specific issue mentioned above was solved already before, but this issue is about the possible optimisation of avoiding the creation of a TCP connection thousands of times unnecessarily. Now...

Update: hooks were added for `sendmsg` (#1778) and `sendto` (#1520), but only for forwarding DNS resolution to the agent.

I think this contradicts #1714 a bit. As a daemon the internal-proxy does not write to the running app's stderr.